Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b45beb6af831bf3f1de84ca83ef4bd002ceb6d6be931661b220e9a566315a2cf

Tx prefix hash: 9c22ad6722759895a29249cc6dbcd9325f89f199edc5255c547f1eaad5e529d5
Tx public key: e5d5c2a7fbaf49911de999900af84dd6a42e93130b066cd6563789b38b257b04
Timestamp: 1634165229 Timestamp [UCT]: 2021-10-13 22:47:09 Age [y:d:h:m:s]: 03:150:18:00:14
Block: 352544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 885265 RingCT/type: yes/0
Extra: 01e5d5c2a7fbaf49911de999900af84dd6a42e93130b066cd6563789b38b257b04021100000021fdc024ec000000000000000000

1 output(s) for total of 41.675018366000 dcy

stealth address amount amount idx
00: 6be1f1f59ef27d1c9e33144dd39b2b4b643c99981be4a3934bb80bfa78dce494 41.675018366000 720626 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": 352554, "vin": [ { "gen": { "height": 352544 } } ], "vout": [ { "amount": 41675018366, "target": { "key": "6be1f1f59ef27d1c9e33144dd39b2b4b643c99981be4a3934bb80bfa78dce494" } } ], "extra": [ 1, 229, 213, 194, 167, 251, 175, 73, 145, 29, 233, 153, 144, 10, 248, 77, 214, 164, 46, 147, 19, 11, 6, 108, 214, 86, 55, 137, 179, 139, 37, 123, 4, 2, 17, 0, 0, 0, 33, 253, 192, 36, 236, 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