Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c54da0654e929af54953fa29b9ea182280f8230e125cd83740c2b55d9304822c

Tx prefix hash: 7e662dba2751c9ee5b0e1cae30b937e99b9f4a2ef877867ceb0d5a81de1cd06c
Tx public key: bc288052feea14837cf801be766c9e9e3cb7c84d3355bf3b954a4526b5974dcc
Timestamp: 1749609611 Timestamp [UCT]: 2025-06-11 02:40:11 Age [y:d:h:m:s]: 00:152:17:05:31
Block: 1302473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106824 RingCT/type: yes/0
Extra: 01bc288052feea14837cf801be766c9e9e3cb7c84d3355bf3b954a4526b5974dcc02110000000fbf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 281f96458c180de7424728b84baae634272e6a6017a7d8a0c0dad1902b6ef2f2 0.600000000000 1790044 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": 1302483, "vin": [ { "gen": { "height": 1302473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "281f96458c180de7424728b84baae634272e6a6017a7d8a0c0dad1902b6ef2f2" } } ], "extra": [ 1, 188, 40, 128, 82, 254, 234, 20, 131, 124, 248, 1, 190, 118, 108, 158, 158, 60, 183, 200, 77, 51, 85, 191, 59, 149, 74, 69, 38, 181, 151, 77, 204, 2, 17, 0, 0, 0, 15, 191, 81, 178, 162, 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