Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 361de9117e3ee7337e3fa97967c839d9c90442dc97284c28d26a09997e0ebc5f

Tx prefix hash: 5657334860bf617d6c7f45d0c750407c9758d13c739788d3f84cd60f872f2e3f
Tx public key: 9d8ef0f2a394710a2e9acd607dcbcf6d46827563ca965d42201c67ff276bba35
Timestamp: 1734869728 Timestamp [UCT]: 2024-12-22 12:15:28 Age [y:d:h:m:s]: 00:096:06:55:55
Block: 1180741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68579 RingCT/type: yes/0
Extra: 019d8ef0f2a394710a2e9acd607dcbcf6d46827563ca965d42201c67ff276bba350211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25b44d24ecd171e92df1ba8b8995c3de192bb51782cf8319da098d2a4e75356c 0.600000000000 1667154 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": 1180751, "vin": [ { "gen": { "height": 1180741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25b44d24ecd171e92df1ba8b8995c3de192bb51782cf8319da098d2a4e75356c" } } ], "extra": [ 1, 157, 142, 240, 242, 163, 148, 113, 10, 46, 154, 205, 96, 125, 203, 207, 109, 70, 130, 117, 99, 202, 150, 93, 66, 32, 28, 103, 255, 39, 107, 186, 53, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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