Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a3179a99ab676f79c93fa54aea6d0f875a8fb5efb65b5c484c579e60b004e2d

Tx prefix hash: 8d02c775c45280e34a850d62f8d73ede0f119a8d2f8e7f7f1793c06b6ffe19d3
Tx public key: 5602c6858773933ecb6446328fa287729513ee25bb9cd5c15f7a8c69176b733f
Timestamp: 1711290689 Timestamp [UCT]: 2024-03-24 14:31:29 Age [y:d:h:m:s]: 00:361:08:27:20
Block: 985369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258363 RingCT/type: yes/0
Extra: 015602c6858773933ecb6446328fa287729513ee25bb9cd5c15f7a8c69176b733f02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bc84dac50c27479d517a6fd16f1183d49ebdc98a7c3ea908d9db94ef3ca803f 0.600000000000 1445578 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": 985379, "vin": [ { "gen": { "height": 985369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bc84dac50c27479d517a6fd16f1183d49ebdc98a7c3ea908d9db94ef3ca803f" } } ], "extra": [ 1, 86, 2, 198, 133, 135, 115, 147, 62, 203, 100, 70, 50, 143, 162, 135, 114, 149, 19, 238, 37, 187, 156, 213, 193, 95, 122, 140, 105, 23, 107, 115, 63, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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