Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 283e81eaa6f341c8809d08b4113269ea57d59e0d4821435dd143ecd9ffc5d032

Tx prefix hash: d905f49c663d3cf0b1b9303d89e1291b932f01fe2b18e102cb28ec24f3f46e9f
Tx public key: 72816b44fdf2faa09715c7989484460d17e7de1882d0567b51d1e8c77b51c40f
Timestamp: 1762461458 Timestamp [UCT]: 2025-11-06 20:37:38 Age [y:d:h:m:s]: 00:047:03:37:23
Block: 1406451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33756 RingCT/type: yes/0
Extra: 0172816b44fdf2faa09715c7989484460d17e7de1882d0567b51d1e8c77b51c40f02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 826eada1660f4fda37a255474e5e99802edd30206d6319d4d8ca38f85e25713a 0.600000000000 1894836 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": 1406461, "vin": [ { "gen": { "height": 1406451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "826eada1660f4fda37a255474e5e99802edd30206d6319d4d8ca38f85e25713a" } } ], "extra": [ 1, 114, 129, 107, 68, 253, 242, 250, 160, 151, 21, 199, 152, 148, 132, 70, 13, 23, 231, 222, 24, 130, 208, 86, 123, 81, 209, 232, 199, 123, 81, 196, 15, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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