Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df335bd461aa2cb35c3cb80319c47e33aa918abf2596ee330a45061c1a717463

Tx prefix hash: 2ec0e3006fc357332085ceccfbf41e4ef965485a9992236a97e34b1ea9770ef5
Tx public key: 5d6b7b5037415786601e2c2df2f0aa23df928f4e5e6378153883f281bc7ba4e4
Timestamp: 1745855243 Timestamp [UCT]: 2025-04-28 15:47:23 Age [y:d:h:m:s]: 00:008:03:55:56
Block: 1271401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5834 RingCT/type: yes/0
Extra: 015d6b7b5037415786601e2c2df2f0aa23df928f4e5e6378153883f281bc7ba4e40211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69898f0cf6241840b310f3a1aa66602e45ebec36106850091262a0e238991f27 0.600000000000 1758662 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": 1271411, "vin": [ { "gen": { "height": 1271401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69898f0cf6241840b310f3a1aa66602e45ebec36106850091262a0e238991f27" } } ], "extra": [ 1, 93, 107, 123, 80, 55, 65, 87, 134, 96, 30, 44, 45, 242, 240, 170, 35, 223, 146, 143, 78, 94, 99, 120, 21, 56, 131, 242, 129, 188, 123, 164, 228, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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