Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f19281a48269a83460b1e7bcd601b55951c9317db734b1715c89741a24fd415

Tx prefix hash: 00d1ce78a6f045b07228c9ab8f5dc9076bf4957c8c65f9d63bd143ad30184a77
Tx public key: 6252c1d8d7f0d01b6cf461db249e0399108d1cd8b830d5a6211cc38af8e5eec3
Timestamp: 1696629782 Timestamp [UCT]: 2023-10-06 22:03:02 Age [y:d:h:m:s]: 01:180:12:57:12
Block: 864002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390078 RingCT/type: yes/0
Extra: 016252c1d8d7f0d01b6cf461db249e0399108d1cd8b830d5a6211cc38af8e5eec302110000000c75e3f0e9000000000000000000

1 output(s) for total of 0.841788030000 dcy

stealth address amount amount idx
00: 002326d7455b35853efb3290b322213c9692f625bdc5bd37412c5e60fdc8f82a 0.841788030000 1318506 of 0

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": 864012, "vin": [ { "gen": { "height": 864002 } } ], "vout": [ { "amount": 841788030, "target": { "key": "002326d7455b35853efb3290b322213c9692f625bdc5bd37412c5e60fdc8f82a" } } ], "extra": [ 1, 98, 82, 193, 216, 215, 240, 208, 27, 108, 244, 97, 219, 36, 158, 3, 153, 16, 141, 28, 216, 184, 48, 213, 166, 33, 28, 195, 138, 248, 229, 238, 195, 2, 17, 0, 0, 0, 12, 117, 227, 240, 233, 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