Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68ab571037157480a18adf75bb565ec6e0703b20e7c1e2daf5bfb3ab298196e1

Tx prefix hash: eb0aeb3568211acefa34ee2bec32b16a3b8ef3ff880de3c9eb0bc3eba44bbfc0
Tx public key: 1b1ff2fad6272f323354f922355491cfd7a0bb37c78bf0c255e1fdff2bc8bd1f
Timestamp: 1656989792 Timestamp [UCT]: 2022-07-05 02:56:32 Age [y:d:h:m:s]: 02:134:10:43:24
Block: 536867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 617406 RingCT/type: yes/0
Extra: 011b1ff2fad6272f323354f922355491cfd7a0bb37c78bf0c255e1fdff2bc8bd1f021100000001cb8520c2000000000000000000

1 output(s) for total of 10.212613976000 dcy

stealth address amount amount idx
00: b49d392dcd1f8807bd26cc98440e3e143700a68064c30ec09e9ee29caff200a9 10.212613976000 966674 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": 536877, "vin": [ { "gen": { "height": 536867 } } ], "vout": [ { "amount": 10212613976, "target": { "key": "b49d392dcd1f8807bd26cc98440e3e143700a68064c30ec09e9ee29caff200a9" } } ], "extra": [ 1, 27, 31, 242, 250, 214, 39, 47, 50, 51, 84, 249, 34, 53, 84, 145, 207, 215, 160, 187, 55, 199, 139, 240, 194, 85, 225, 253, 255, 43, 200, 189, 31, 2, 17, 0, 0, 0, 1, 203, 133, 32, 194, 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