Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 676e97502dedce5df3e5d1d535984e6215afcd415a867fb56154938f39410611

Tx prefix hash: 0463c971570c7cda9f4b755e44440e3c052bf2b73c564525c1bd160813818829
Tx public key: 838cc609cb3efe1b8fb16b7882722b9f6db4bb89de7f806b2801e1d3e9178e10
Timestamp: 1736513481 Timestamp [UCT]: 2025-01-10 12:51:21 Age [y:d:h:m:s]: 00:164:02:29:01
Block: 1194318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116888 RingCT/type: yes/0
Extra: 01838cc609cb3efe1b8fb16b7882722b9f6db4bb89de7f806b2801e1d3e9178e10021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d19eb3285628fe40c0e4a0dbc0aa2d36b509c9dc45888c1c2997a383d0a387ca 0.600000000000 1680887 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": 1194328, "vin": [ { "gen": { "height": 1194318 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d19eb3285628fe40c0e4a0dbc0aa2d36b509c9dc45888c1c2997a383d0a387ca" } } ], "extra": [ 1, 131, 140, 198, 9, 203, 62, 254, 27, 143, 177, 107, 120, 130, 114, 43, 159, 109, 180, 187, 137, 222, 127, 128, 107, 40, 1, 225, 211, 233, 23, 142, 16, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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