Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: c676bf900284aa3c5352a70adc4bd25f0dd38be2c7a467eb3d52f064bd82d9dd

Tx prefix hash: 9ba14b2b7ff3d42ae910778e320f2a87be14a867182353e7c26ca1d9ffbfc481
Tx public key: 92999b1a3aa9f0968fc565d9e8a6e9cec02e8d85d67fcb1cd6acddea84b4fe42
Timestamp: 1710133468 Timestamp [UCT]: 2024-03-11 05:04:28 Age [y:d:h:m:s]: 01:023:15:05:31
Block: 975766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277862 RingCT/type: yes/0
Extra: 0192999b1a3aa9f0968fc565d9e8a6e9cec02e8d85d67fcb1cd6acddea84b4fe4202110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1adce0052d65c6b7ba9bf16e1d02bc994fc3d3fb7bfec4092043c470c66fe3cb 0.600000000000 1435741 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 975776, "vin": [ { "gen": { "height": 975766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1adce0052d65c6b7ba9bf16e1d02bc994fc3d3fb7bfec4092043c470c66fe3cb" } } ], "extra": [ 1, 146, 153, 155, 26, 58, 169, 240, 150, 143, 197, 101, 217, 232, 166, 233, 206, 192, 46, 141, 133, 214, 127, 203, 28, 214, 172, 221, 234, 132, 180, 254, 66, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8