Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49f716d1daec711535eb79a51a02fdb1f6f4fe8a356c04f2c6efe7722a17c467

Tx prefix hash: 278ffed75182b3ef233422759b77c9ed38d8c69c8103e1d1977d075ce3ccbb63
Tx public key: 401648911f8758b9a4bd4c456626880bd2a33d8d3d6144f516c5e9c74d031e93
Timestamp: 1763222964 Timestamp [UCT]: 2025-11-15 16:09:24 Age [y:d:h:m:s]: 00:048:15:34:27
Block: 1412763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34848 RingCT/type: yes/0
Extra: 01401648911f8758b9a4bd4c456626880bd2a33d8d3d6144f516c5e9c74d031e930211000000028ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9ea124ef567c6cb20e11c9dfa086478a37aa7afe89bcdb19866691ac79903fa 0.600000000000 1901236 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": 1412773, "vin": [ { "gen": { "height": 1412763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9ea124ef567c6cb20e11c9dfa086478a37aa7afe89bcdb19866691ac79903fa" } } ], "extra": [ 1, 64, 22, 72, 145, 31, 135, 88, 185, 164, 189, 76, 69, 102, 38, 136, 11, 210, 163, 61, 141, 61, 97, 68, 245, 22, 197, 233, 199, 77, 3, 30, 147, 2, 17, 0, 0, 0, 2, 140, 235, 127, 9, 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