Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66532f2f4bfab61f4c6e930a39418a811e9c3fcd25098600e7fa347d4e22db07

Tx prefix hash: e6c074bf4a1e39c489494600eb32623f87d4cfd64e02ffa578e7070b4c409986
Tx public key: f4b403a27fd0d0bbe5e9e56050aae8daeda33d70684465950c7e637dc8d64824
Timestamp: 1623767716 Timestamp [UCT]: 2021-06-15 14:35:16 Age [y:d:h:m:s]: 03:165:20:12:52
Block: 278327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 884461 RingCT/type: yes/0
Extra: 01f4b403a27fd0d0bbe5e9e56050aae8daeda33d70684465950c7e637dc8d64824021100000005ece3035d000000000000000000

1 output(s) for total of 73.416748173000 dcy

stealth address amount amount idx
00: 0ca6a185adced9ab237e630edfa3c5311cb0d288c0357fc9583e5526ef722595 73.416748173000 583243 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": 278337, "vin": [ { "gen": { "height": 278327 } } ], "vout": [ { "amount": 73416748173, "target": { "key": "0ca6a185adced9ab237e630edfa3c5311cb0d288c0357fc9583e5526ef722595" } } ], "extra": [ 1, 244, 180, 3, 162, 127, 208, 208, 187, 229, 233, 229, 96, 80, 170, 232, 218, 237, 163, 61, 112, 104, 68, 101, 149, 12, 126, 99, 125, 200, 214, 72, 36, 2, 17, 0, 0, 0, 5, 236, 227, 3, 93, 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