Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07c73972fdb4fb15a576996419acb262d77e920295450b397c92d7c8a8d07f86

Tx prefix hash: 248767ce784816f2109f529e08493e617fff6b29b09666fed561238611799376
Tx public key: bda2ccc804d1547c59b25f41f60594a3a95a10992aa257032d36ae42d90a925b
Timestamp: 1756528552 Timestamp [UCT]: 2025-08-30 04:35:52 Age [y:d:h:m:s]: 00:068:17:39:42
Block: 1357442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49063 RingCT/type: yes/0
Extra: 01bda2ccc804d1547c59b25f41f60594a3a95a10992aa257032d36ae42d90a925b021100000006b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78b8e1b8c275acfba755ebae81cad883d17e3b6653270d77ff7a9be1df79fafb 0.600000000000 1845451 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": 1357452, "vin": [ { "gen": { "height": 1357442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78b8e1b8c275acfba755ebae81cad883d17e3b6653270d77ff7a9be1df79fafb" } } ], "extra": [ 1, 189, 162, 204, 200, 4, 209, 84, 124, 89, 178, 95, 65, 246, 5, 148, 163, 169, 90, 16, 153, 42, 162, 87, 3, 45, 54, 174, 66, 217, 10, 146, 91, 2, 17, 0, 0, 0, 6, 178, 247, 132, 196, 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