Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e5fd4d9de22734db14ec2311b1b80d7d97eefc1ab5546fb5f2e9e4470439403

Tx prefix hash: cbcf18d718e9a305f085be95690adb06a14df5d083b9805829594db12549d546
Tx public key: 4d6af1b7f8f6f88160bcf85eca84a5e54bc495ff9fcaf07f97c2ab7694427cab
Timestamp: 1736863732 Timestamp [UCT]: 2025-01-14 14:08:52 Age [y:d:h:m:s]: 00:061:08:24:36
Block: 1197222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43630 RingCT/type: yes/0
Extra: 014d6af1b7f8f6f88160bcf85eca84a5e54bc495ff9fcaf07f97c2ab7694427cab0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae88fcd0d3e7d2340e89c84dbc69242a5c3b17dd5598ba23451d9276b158d60e 0.600000000000 1683829 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": 1197232, "vin": [ { "gen": { "height": 1197222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae88fcd0d3e7d2340e89c84dbc69242a5c3b17dd5598ba23451d9276b158d60e" } } ], "extra": [ 1, 77, 106, 241, 183, 248, 246, 248, 129, 96, 188, 248, 94, 202, 132, 165, 229, 75, 196, 149, 255, 159, 202, 240, 127, 151, 194, 171, 118, 148, 66, 124, 171, 2, 17, 0, 0, 0, 1, 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