Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e76e1f67dba3e23f014c0f93a4db320ce221b5bcff3642066945e00636b74721

Tx prefix hash: 600b75403163813739a55c966072a845bff658ea34d9d2705ad655032981f326
Tx public key: 463b5e9e978256d2473ff0d526a5bc802c1681b311ebf7206c8df0dfd2b60abc
Timestamp: 1726045477 Timestamp [UCT]: 2024-09-11 09:04:37 Age [y:d:h:m:s]: 00:118:02:08:19
Block: 1107673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84449 RingCT/type: yes/0
Extra: 01463b5e9e978256d2473ff0d526a5bc802c1681b311ebf7206c8df0dfd2b60abc021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 881a650311bf60bd30d8db332a5bc97da0cae8aa818fc57b89046b399311e1aa 0.600000000000 1585294 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": 1107683, "vin": [ { "gen": { "height": 1107673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "881a650311bf60bd30d8db332a5bc97da0cae8aa818fc57b89046b399311e1aa" } } ], "extra": [ 1, 70, 59, 94, 158, 151, 130, 86, 210, 71, 63, 240, 213, 38, 165, 188, 128, 44, 22, 129, 179, 17, 235, 247, 32, 108, 141, 240, 223, 210, 182, 10, 188, 2, 17, 0, 0, 0, 7, 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