Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73f0cabb19c85cbe5779153a4b79017fc0727d56463035aa5a7aac9b29763886

Tx prefix hash: 5de2c5e27ef3af0c04eaa5e3da948f413f044c9ad78986e5bd2ebd37defb8786
Tx public key: d913812b91e033f079a4731e248f72c076d09c6dc19512708a79c955efcae6d5
Timestamp: 1729590151 Timestamp [UCT]: 2024-10-22 09:42:31 Age [y:d:h:m:s]: 00:074:02:09:26
Block: 1137033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52971 RingCT/type: yes/0
Extra: 01d913812b91e033f079a4731e248f72c076d09c6dc19512708a79c955efcae6d5021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1d105c760688b4213dfc3a64000188c9a985946a551906c95aaf2cae3e9b57e 0.600000000000 1620448 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": 1137043, "vin": [ { "gen": { "height": 1137033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1d105c760688b4213dfc3a64000188c9a985946a551906c95aaf2cae3e9b57e" } } ], "extra": [ 1, 217, 19, 129, 43, 145, 224, 51, 240, 121, 164, 115, 30, 36, 143, 114, 192, 118, 208, 156, 109, 193, 149, 18, 112, 138, 121, 201, 85, 239, 202, 230, 213, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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