Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7544d5a01c4e54d3838d20da02027e59d9a7cf0a22296a731f7c7d67b899574

Tx prefix hash: 56651776f471e7d0e7a69f55c4fafc72326140bbc773ab217dfb74799b41684c
Tx public key: 16d03b667c4b64f0101747a91a4ccf9ce956827839f6d62a21c7492f21806628
Timestamp: 1728248018 Timestamp [UCT]: 2024-10-06 20:53:38 Age [y:d:h:m:s]: 01:034:20:24:53
Block: 1125930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283291 RingCT/type: yes/0
Extra: 0116d03b667c4b64f0101747a91a4ccf9ce956827839f6d62a21c7492f21806628021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af4cc0bb1fbddaead1a1c3ff2a0c1d6a719d7e16d782cae559104ade938b833c 0.600000000000 1608703 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": 1125940, "vin": [ { "gen": { "height": 1125930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af4cc0bb1fbddaead1a1c3ff2a0c1d6a719d7e16d782cae559104ade938b833c" } } ], "extra": [ 1, 22, 208, 59, 102, 124, 75, 100, 240, 16, 23, 71, 169, 26, 76, 207, 156, 233, 86, 130, 120, 57, 246, 214, 42, 33, 199, 73, 47, 33, 128, 102, 40, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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