Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88fffb9aa41ff166a5343e3cbcd97ff20b646e9de9c3728b7918a72dd660d758

Tx prefix hash: 0031903fd96d746bfa19f2a2000255cc2911fecf4528693e3121b54e71b12e92
Tx public key: ad8f78c9bce60946797ffb9f8aed70c26b08202d686e937c9e8cd57c3f769cbc
Timestamp: 1704521818 Timestamp [UCT]: 2024-01-06 06:16:58 Age [y:d:h:m:s]: 01:306:11:30:03
Block: 929212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477879 RingCT/type: yes/0
Extra: 01ad8f78c9bce60946797ffb9f8aed70c26b08202d686e937c9e8cd57c3f769cbc0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38eb2fd301473bad819a47d51d2f2fe61943e105ebc3a0f5c844c24bbf96324d 0.600000000000 1387080 of 15

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": 929222, "vin": [ { "gen": { "height": 929212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38eb2fd301473bad819a47d51d2f2fe61943e105ebc3a0f5c844c24bbf96324d" } } ], "extra": [ 1, 173, 143, 120, 201, 188, 230, 9, 70, 121, 127, 251, 159, 138, 237, 112, 194, 107, 8, 32, 45, 104, 110, 147, 124, 158, 140, 213, 124, 63, 118, 156, 188, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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