Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55b067e01acee86aab2465f30c24ce0ef13dc6460b985ad421b80f56d9aef6d6

Tx prefix hash: 9cd9e7a1367247882142f2b26bd88568b04defbce232b84f327dbdf9decd2f67
Tx public key: e038f8ddaf356baf1e3c758f10d9836f8c2e56900aa0bcd6c4a9900243cd9bba
Timestamp: 1713408472 Timestamp [UCT]: 2024-04-18 02:47:52 Age [y:d:h:m:s]: 01:220:22:06:58
Block: 1002894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416579 RingCT/type: yes/0
Extra: 01e038f8ddaf356baf1e3c758f10d9836f8c2e56900aa0bcd6c4a9900243cd9bba0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 536af52d28c701b5209d96ec9293fa552551b3459647fed7e59f5cb94c07e821 0.600000000000 1463424 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": 1002904, "vin": [ { "gen": { "height": 1002894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "536af52d28c701b5209d96ec9293fa552551b3459647fed7e59f5cb94c07e821" } } ], "extra": [ 1, 224, 56, 248, 221, 175, 53, 107, 175, 30, 60, 117, 143, 16, 217, 131, 111, 140, 46, 86, 144, 10, 160, 188, 214, 196, 169, 144, 2, 67, 205, 155, 186, 2, 17, 0, 0, 0, 2, 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