Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcdcd003b5080211c3e5f1261a247822e2566b658058c69fc9bb6e70e52b1b9a

Tx prefix hash: b2712d6727eb4f70821bec650434293e892e3b099142a6f5e63c3371bad8c4c3
Tx public key: d85da4ce1a1695b8f43c5310d9adc5ed24e76b3cd597a0267bde31d9225f7deb
Timestamp: 1697116222 Timestamp [UCT]: 2023-10-12 13:10:22 Age [y:d:h:m:s]: 01:091:18:33:46
Block: 868051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326832 RingCT/type: yes/0
Extra: 01d85da4ce1a1695b8f43c5310d9adc5ed24e76b3cd597a0267bde31d9225f7deb02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.816181454000 dcy

stealth address amount amount idx
00: fd7190766665ed70232a8dc6f7290664f162610d143bf9baaba979ed2268c095 0.816181454000 1322808 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": 868061, "vin": [ { "gen": { "height": 868051 } } ], "vout": [ { "amount": 816181454, "target": { "key": "fd7190766665ed70232a8dc6f7290664f162610d143bf9baaba979ed2268c095" } } ], "extra": [ 1, 216, 93, 164, 206, 26, 22, 149, 184, 244, 60, 83, 16, 217, 173, 197, 237, 36, 231, 107, 60, 213, 151, 160, 38, 123, 222, 49, 217, 34, 95, 125, 235, 2, 17, 0, 0, 0, 4, 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