Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85de4f17848f7178a9524a5391a259fcdd7274514c3eed211d589a92dc145787

Tx prefix hash: 6e7bbd0830cb3b3835efe8eb1a1db1ee2bcce9e92781ee6a2690efbc74502b71
Tx public key: 987a974ffce26a4e59da0deecee6c91135d4f12a4992a99fce3d73b39091e56f
Timestamp: 1648662903 Timestamp [UCT]: 2022-03-30 17:55:03 Age [y:d:h:m:s]: 02:241:07:47:19
Block: 469741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 692050 RingCT/type: yes/0
Extra: 01987a974ffce26a4e59da0deecee6c91135d4f12a4992a99fce3d73b39091e56f02110000000fc9067537000000000000000000

1 output(s) for total of 17.043285459000 dcy

stealth address amount amount idx
00: 5270d9a3ea400ce77509cf4659ea8f6d47e6e495d17bf63c416e2add50b528c2 17.043285459000 888739 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": 469751, "vin": [ { "gen": { "height": 469741 } } ], "vout": [ { "amount": 17043285459, "target": { "key": "5270d9a3ea400ce77509cf4659ea8f6d47e6e495d17bf63c416e2add50b528c2" } } ], "extra": [ 1, 152, 122, 151, 79, 252, 226, 106, 78, 89, 218, 13, 238, 206, 230, 201, 17, 53, 212, 241, 42, 73, 146, 169, 159, 206, 61, 115, 179, 144, 145, 229, 111, 2, 17, 0, 0, 0, 15, 201, 6, 117, 55, 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