Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 811d04d6cc8b240f99798b233b83d8ef78da6604217c5e9b991a2b1ddfe2e4c2

Tx prefix hash: c0cc3f47916da4816e2d076087967e9b7cb04b9eca42ff0e04ff0624455f63cb
Tx public key: bfe835ecdb66826c3e4a22fa6c4b948ce85a209a97fbff2daed9476e57762bbf
Timestamp: 1727693258 Timestamp [UCT]: 2024-09-30 10:47:38 Age [y:d:h:m:s]: 00:114:13:04:46
Block: 1121342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81855 RingCT/type: yes/0
Extra: 01bfe835ecdb66826c3e4a22fa6c4b948ce85a209a97fbff2daed9476e57762bbf02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 710c42519033267c863939313d194eae4b66dc69a3fe513584c42ad7d872ac31 0.600000000000 1603581 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": 1121352, "vin": [ { "gen": { "height": 1121342 } } ], "vout": [ { "amount": 600000000, "target": { "key": "710c42519033267c863939313d194eae4b66dc69a3fe513584c42ad7d872ac31" } } ], "extra": [ 1, 191, 232, 53, 236, 219, 102, 130, 108, 62, 74, 34, 250, 108, 75, 148, 140, 232, 90, 32, 154, 151, 251, 255, 45, 174, 217, 71, 110, 87, 118, 43, 191, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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