Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7698385658e7f8f2d6e739db3e54612f97cb3ac8405b5dc415a271ca84c80ca

Tx prefix hash: 2cb205db5b9b09e69ee3b1362cc3283cc023790eb9bd55d10f953d75b6f461f2
Tx public key: a98180432344efa3e685f4ec3a24357b1c0e0a7cb28dfe1f0b46caab27372e1f
Timestamp: 1761798494 Timestamp [UCT]: 2025-10-30 04:28:14 Age [y:d:h:m:s]: 00:010:17:36:13
Block: 1400973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7684 RingCT/type: yes/0
Extra: 01a98180432344efa3e685f4ec3a24357b1c0e0a7cb28dfe1f0b46caab27372e1f02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd79296b1ed29f00ca86e890feceed9de5be95c8992b10580906974f375f4b19 0.600000000000 1889292 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": 1400983, "vin": [ { "gen": { "height": 1400973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd79296b1ed29f00ca86e890feceed9de5be95c8992b10580906974f375f4b19" } } ], "extra": [ 1, 169, 129, 128, 67, 35, 68, 239, 163, 230, 133, 244, 236, 58, 36, 53, 123, 28, 14, 10, 124, 178, 141, 254, 31, 11, 70, 202, 171, 39, 55, 46, 31, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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