Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5b2d4c1c3aa7e02503c0590ea6d4bddf6a975abcc85e2a303e49553b9509f2b

Tx prefix hash: 7ec8ac1694834fc147bfa677f3bd146b35a68da96f6700377b401a2a3ebd5678
Tx public key: a59b6662ec863c5758b10fb29a9491b25f63104c28f1efb74b944d9faaf0e998
Timestamp: 1725381171 Timestamp [UCT]: 2024-09-03 16:32:51 Age [y:d:h:m:s]: 00:119:21:21:28
Block: 1102168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85751 RingCT/type: yes/0
Extra: 01a59b6662ec863c5758b10fb29a9491b25f63104c28f1efb74b944d9faaf0e998021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98ffc09ef81c96ffcc65e24f83b6bbe7540659b2c8f1e610a6ca5ad5b17d653c 0.600000000000 1578499 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": 1102178, "vin": [ { "gen": { "height": 1102168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98ffc09ef81c96ffcc65e24f83b6bbe7540659b2c8f1e610a6ca5ad5b17d653c" } } ], "extra": [ 1, 165, 155, 102, 98, 236, 134, 60, 87, 88, 177, 15, 178, 154, 148, 145, 178, 95, 99, 16, 76, 40, 241, 239, 183, 75, 148, 77, 159, 170, 240, 233, 152, 2, 17, 0, 0, 0, 4, 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