Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31d83442e2bca63a92b0f9734b32debdfa76cccba94d468bd3cffe305e0296cb

Tx prefix hash: 4aa48aabc68cc39f2ed4a46fbb7211bdceb3b2f82afbed97ecec7312e4b8292c
Tx public key: bfcec78aefc2dae045dd832e482a616642e1fe58effbfeda5adb0876382aa8a5
Timestamp: 1705999867 Timestamp [UCT]: 2024-01-23 08:51:07 Age [y:d:h:m:s]: 01:077:09:42:29
Block: 941458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316419 RingCT/type: yes/0
Extra: 01bfcec78aefc2dae045dd832e482a616642e1fe58effbfeda5adb0876382aa8a502110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31501f842f105c6a0fb7fb82a69152ddc58f5039da1c3ae927a12cc7bf748bb1 0.600000000000 1399608 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": 941468, "vin": [ { "gen": { "height": 941458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31501f842f105c6a0fb7fb82a69152ddc58f5039da1c3ae927a12cc7bf748bb1" } } ], "extra": [ 1, 191, 206, 199, 138, 239, 194, 218, 224, 69, 221, 131, 46, 72, 42, 97, 102, 66, 225, 254, 88, 239, 251, 254, 218, 90, 219, 8, 118, 56, 42, 168, 165, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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