Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbe9d566f6e7ca83ee56de5cd5b3fecd95d48437ca97287a83e5382e3b9363c9

Tx prefix hash: 5e6dd8a5ad46828526ba8f9c4c12c2346407c6112bf40638a04c59725eeeeb28
Tx public key: 56a4dc76092a0c2e08d1ca3cd6972f077f41a3c3fb4c976be4be60493765aa4e
Timestamp: 1760839075 Timestamp [UCT]: 2025-10-19 01:57:55 Age [y:d:h:m:s]: 00:103:01:47:06
Block: 1393024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73614 RingCT/type: yes/0
Extra: 0156a4dc76092a0c2e08d1ca3cd6972f077f41a3c3fb4c976be4be60493765aa4e02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30579b5e0d150c1ad3929ee28272df3342c9b71c37e97438dd0a2afbbe406399 0.600000000000 1881281 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": 1393034, "vin": [ { "gen": { "height": 1393024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30579b5e0d150c1ad3929ee28272df3342c9b71c37e97438dd0a2afbbe406399" } } ], "extra": [ 1, 86, 164, 220, 118, 9, 42, 12, 46, 8, 209, 202, 60, 214, 151, 47, 7, 127, 65, 163, 195, 251, 76, 151, 107, 228, 190, 96, 73, 55, 101, 170, 78, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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