Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42f0c0b2c6eb964f8aaccf6d18f02d4eea7a1ad54f34558486fc677a6c45f11c

Tx prefix hash: 659fadd2d4a0a7971947eb9372d00fc1c41b6d8f3e2fd3be129a52497d382956
Tx public key: d68dc92cf6e7d825d1cd405a407d48ce5e026cd4d75542372093248a59bb1757
Timestamp: 1730674871 Timestamp [UCT]: 2024-11-03 23:01:11 Age [y:d:h:m:s]: 00:160:04:43:03
Block: 1145969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114327 RingCT/type: yes/0
Extra: 01d68dc92cf6e7d825d1cd405a407d48ce5e026cd4d75542372093248a59bb17570211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fcd52fb6d34b069fe001008ffa37ffa54ae6c532fac22020584103e67fcd878 0.600000000000 1630508 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": 1145979, "vin": [ { "gen": { "height": 1145969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fcd52fb6d34b069fe001008ffa37ffa54ae6c532fac22020584103e67fcd878" } } ], "extra": [ 1, 214, 141, 201, 44, 246, 231, 216, 37, 209, 205, 64, 90, 64, 125, 72, 206, 94, 2, 108, 212, 215, 85, 66, 55, 32, 147, 36, 138, 89, 187, 23, 87, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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