Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0f1bdb17bf82e0a96a75a6b56cadaeb712b389afa95828ad0c6e645144a542c

Tx prefix hash: 44d1025b4900b04d1e8b4ff77521eb748c5c2dc8b361d6f446e6cef2b0a26f33
Tx public key: f42c100792475fefdd35807bd0d0ff85df78c0a0634cfef726dfff8ddae6bf15
Timestamp: 1703689948 Timestamp [UCT]: 2023-12-27 15:12:28 Age [y:d:h:m:s]: 01:134:20:15:24
Block: 922338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357502 RingCT/type: yes/0
Extra: 01f42c100792475fefdd35807bd0d0ff85df78c0a0634cfef726dfff8ddae6bf1502110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1423699e54e07b8e005e903a2b14a3e1b167755fcc7b420fc1699a703ae24d0d 0.600000000000 1380034 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": 922348, "vin": [ { "gen": { "height": 922338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1423699e54e07b8e005e903a2b14a3e1b167755fcc7b420fc1699a703ae24d0d" } } ], "extra": [ 1, 244, 44, 16, 7, 146, 71, 95, 239, 221, 53, 128, 123, 208, 208, 255, 133, 223, 120, 192, 160, 99, 76, 254, 247, 38, 223, 255, 141, 218, 230, 191, 21, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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