Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f59dcc5d2d1c505f150aad5e53cc76024b19acd65cefe2f9df5f00d16c01cbd

Tx prefix hash: c3df3c53de8d1e812b74e6701938fa483513848db4bf42a25303511cf3725d1f
Tx public key: fe88ce83e9e3296ed1dbe2900c977d1eccc4f41f0280dd9028a39e46ce541180
Timestamp: 1670353065 Timestamp [UCT]: 2022-12-06 18:57:45 Age [y:d:h:m:s]: 02:120:18:33:23
Block: 646859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 608006 RingCT/type: yes/0
Extra: 01fe88ce83e9e3296ed1dbe2900c977d1eccc4f41f0280dd9028a39e46ce54118002110000000375e3f0e9000000000000000000

1 output(s) for total of 4.412529280000 dcy

stealth address amount amount idx
00: c878e69fa68ebd4f7723f2704f5ab5abf35f9c0bf2a09832dca3d8e968fcd10c 4.412529280000 1087100 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": 646869, "vin": [ { "gen": { "height": 646859 } } ], "vout": [ { "amount": 4412529280, "target": { "key": "c878e69fa68ebd4f7723f2704f5ab5abf35f9c0bf2a09832dca3d8e968fcd10c" } } ], "extra": [ 1, 254, 136, 206, 131, 233, 227, 41, 110, 209, 219, 226, 144, 12, 151, 125, 30, 204, 196, 244, 31, 2, 128, 221, 144, 40, 163, 158, 70, 206, 84, 17, 128, 2, 17, 0, 0, 0, 3, 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