Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6658f870b631832d726ba5eeab2f1bf57f8a7a7ee89b607e7a1d18aa32ee7219

Tx prefix hash: 37f7232a716a5734ef5ed8757c8245bbe90802b43f521b67399249868adf28af
Tx public key: 0bf67def51e1b7f8a7971b3640b98553c99949ec6e758a95cde6c964f847fe79
Timestamp: 1652643212 Timestamp [UCT]: 2022-05-15 19:33:32 Age [y:d:h:m:s]: 03:169:16:14:36
Block: 501701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 900208 RingCT/type: yes/0
Extra: 010bf67def51e1b7f8a7971b3640b98553c99949ec6e758a95cde6c964f847fe790211000000092e6b1fd5000000000000000000

1 output(s) for total of 13.355388443000 dcy

stealth address amount amount idx
00: e200901d92360b4fdc8906bba69d79e56c34f6596ba74c1d9db172e3de1f2855 13.355388443000 926404 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": 501711, "vin": [ { "gen": { "height": 501701 } } ], "vout": [ { "amount": 13355388443, "target": { "key": "e200901d92360b4fdc8906bba69d79e56c34f6596ba74c1d9db172e3de1f2855" } } ], "extra": [ 1, 11, 246, 125, 239, 81, 225, 183, 248, 167, 151, 27, 54, 64, 185, 133, 83, 201, 153, 73, 236, 110, 117, 138, 149, 205, 230, 201, 100, 248, 71, 254, 121, 2, 17, 0, 0, 0, 9, 46, 107, 31, 213, 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