Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6acf7c8d05d6fab4a414f9ee624dc9b67cbb1b193b13d7cfce519488d4bbf25b

Tx prefix hash: cf85b18c87380d60b37349048eb1bb13670b53aa245a3c414201f4ed54fd64dd
Tx public key: 678747adfc7ff80b31ae7deeeacf807c2abd56d6dfc2cc8a9694e6058617675c
Timestamp: 1713807712 Timestamp [UCT]: 2024-04-22 17:41:52 Age [y:d:h:m:s]: 00:308:06:09:15
Block: 1006215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220339 RingCT/type: yes/0
Extra: 01678747adfc7ff80b31ae7deeeacf807c2abd56d6dfc2cc8a9694e6058617675c02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17bd3e4b26ce004fa25a00afc4948143bc6349c2eed9e4b19ab6410a0b2307d4 0.600000000000 1467165 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": 1006225, "vin": [ { "gen": { "height": 1006215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17bd3e4b26ce004fa25a00afc4948143bc6349c2eed9e4b19ab6410a0b2307d4" } } ], "extra": [ 1, 103, 135, 71, 173, 252, 127, 248, 11, 49, 174, 125, 238, 234, 207, 128, 124, 42, 189, 86, 214, 223, 194, 204, 138, 150, 148, 230, 5, 134, 23, 103, 92, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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