Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f0f9ba31813f3e5cc48ee9f5160735383c80196131d73e1ebcb13995d44c258

Tx prefix hash: b7c2d96690e7587a7dca37802b47a9244aedd3b757c0f80298dcae44ac7ba513
Tx public key: 72b65dd8a8984a8fe8f0ee76a47aafb909bc4072a7ea65901975a868f85802f0
Timestamp: 1749144616 Timestamp [UCT]: 2025-06-05 17:30:16 Age [y:d:h:m:s]: 00:161:15:20:14
Block: 1298649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113191 RingCT/type: yes/0
Extra: 0172b65dd8a8984a8fe8f0ee76a47aafb909bc4072a7ea65901975a868f85802f0021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6da48ab6bd18a37aa20acd320277a8d3b30a8b11249ab5c37d4fd59c040ca4f8 0.600000000000 1786178 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": 1298659, "vin": [ { "gen": { "height": 1298649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6da48ab6bd18a37aa20acd320277a8d3b30a8b11249ab5c37d4fd59c040ca4f8" } } ], "extra": [ 1, 114, 182, 93, 216, 168, 152, 74, 143, 232, 240, 238, 118, 164, 122, 175, 185, 9, 188, 64, 114, 167, 234, 101, 144, 25, 117, 168, 104, 248, 88, 2, 240, 2, 17, 0, 0, 0, 4, 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