Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e264a33a2cf81ba8d294306834639f79e1ac6bb4e8cd67b8ca61ca4676dfebf9

Tx prefix hash: 399ac89cc4c0e2faf7b3f2181a6fa8c361e429af5e4abd7d0d82abb05c5fb946
Tx public key: 7262120e16f7f6e539d591b7251b9101a2b84e3c4287172a3ca275a7bc314c14
Timestamp: 1625036553 Timestamp [UCT]: 2021-06-30 07:02:33 Age [y:d:h:m:s]: 04:127:18:06:03
Block: 285749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118699 RingCT/type: yes/0
Extra: 017262120e16f7f6e539d591b7251b9101a2b84e3c4287172a3ca275a7bc314c1402110000000abffe00bb000000000000000000

1 output(s) for total of 69.376195221000 dcy

stealth address amount amount idx
00: e7664c74ae3daae3ce207cba6d4bcf627b201b47300c893117e9d0789d8c1326 69.376195221000 598368 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": 285759, "vin": [ { "gen": { "height": 285749 } } ], "vout": [ { "amount": 69376195221, "target": { "key": "e7664c74ae3daae3ce207cba6d4bcf627b201b47300c893117e9d0789d8c1326" } } ], "extra": [ 1, 114, 98, 18, 14, 22, 247, 246, 229, 57, 213, 145, 183, 37, 27, 145, 1, 162, 184, 78, 60, 66, 135, 23, 42, 60, 162, 117, 167, 188, 49, 76, 20, 2, 17, 0, 0, 0, 10, 191, 254, 0, 187, 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