Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 098043a2fd6b04a5861d4c9e890a48cfc7de07f16c236910df962720d3ade944

Tx prefix hash: 65ca66d71c7a9e8bba4873f9abaadb1a1a3c0581b14af0b9375480ac104c3e43
Tx public key: 2e8801a053c0d33297dfacd0849c194aa704d1a5bb7300acfbe94173d86b0b32
Timestamp: 1723969500 Timestamp [UCT]: 2024-08-18 08:25:00 Age [y:d:h:m:s]: 00:229:10:41:16
Block: 1090471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163848 RingCT/type: yes/0
Extra: 012e8801a053c0d33297dfacd0849c194aa704d1a5bb7300acfbe94173d86b0b32021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bdb81da82ed3beb2edb166ad876bf63b0c060c55e472d1e41b85dca9d785140 0.600000000000 1565094 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": 1090481, "vin": [ { "gen": { "height": 1090471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bdb81da82ed3beb2edb166ad876bf63b0c060c55e472d1e41b85dca9d785140" } } ], "extra": [ 1, 46, 136, 1, 160, 83, 192, 211, 50, 151, 223, 172, 208, 132, 156, 25, 74, 167, 4, 209, 165, 187, 115, 0, 172, 251, 233, 65, 115, 216, 107, 11, 50, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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