Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ef016bf53215863b4deae2939854b51db56c77133c77163fa3e18cd36b20fd5

Tx prefix hash: 6dc8b297633edceb33e6cf8c33cb3d77b8c8b31f9553f15cfaf837275232c5fa
Tx public key: 12a9a3dfbf742bf7c68d40d2672fde71bf84ab4db9730d54480e366c86f7a2bc
Timestamp: 1577727971 Timestamp [UCT]: 2019-12-30 17:46:11 Age [y:d:h:m:s]: 05:075:07:11:08
Block: 35202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1203576 RingCT/type: yes/0
Extra: 0112a9a3dfbf742bf7c68d40d2672fde71bf84ab4db9730d54480e366c86f7a2bc021100000002d81c26c0000000000000000000

1 output(s) for total of 469.204334665000 dcy

stealth address amount amount idx
00: 29cdcb9db0d07142537327c3a431c2a9f1bdbf2262be536045e96b0dca744b19 469.204334665000 59292 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": 35212, "vin": [ { "gen": { "height": 35202 } } ], "vout": [ { "amount": 469204334665, "target": { "key": "29cdcb9db0d07142537327c3a431c2a9f1bdbf2262be536045e96b0dca744b19" } } ], "extra": [ 1, 18, 169, 163, 223, 191, 116, 43, 247, 198, 141, 64, 210, 103, 47, 222, 113, 191, 132, 171, 77, 185, 115, 13, 84, 72, 14, 54, 108, 134, 247, 162, 188, 2, 17, 0, 0, 0, 2, 216, 28, 38, 192, 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