Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f221c75a7ec7a9bf2727cafdd40afe5c5473c1a65e93a05fca15e9784afa1e8

Tx prefix hash: a41c7dec16c318cdad73b761ca621bc061e6b21ff5da75f7e196a2566325ae3a
Tx public key: 32f7736cf13a0e8770ef89485da45ec36ba75cf7c7768fe727aecc7fc38ea39a
Timestamp: 1694262857 Timestamp [UCT]: 2023-09-09 12:34:17 Age [y:d:h:m:s]: 01:172:22:44:33
Block: 844359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384684 RingCT/type: yes/0
Extra: 0132f7736cf13a0e8770ef89485da45ec36ba75cf7c7768fe727aecc7fc38ea39a02110000000933af99f4000000000000000000

1 output(s) for total of 0.977885908000 dcy

stealth address amount amount idx
00: 05eed162ada01a542da5ec9bcfe8781ea3e5a0116ab915d9ca4dc5ffcbb93a2e 0.977885908000 1297663 of 0

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": 844369, "vin": [ { "gen": { "height": 844359 } } ], "vout": [ { "amount": 977885908, "target": { "key": "05eed162ada01a542da5ec9bcfe8781ea3e5a0116ab915d9ca4dc5ffcbb93a2e" } } ], "extra": [ 1, 50, 247, 115, 108, 241, 58, 14, 135, 112, 239, 137, 72, 93, 164, 94, 195, 107, 167, 92, 247, 199, 118, 143, 231, 39, 174, 204, 127, 195, 142, 163, 154, 2, 17, 0, 0, 0, 9, 51, 175, 153, 244, 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