Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e735cad78e6664effd71b4e5cf293e728e663c2df080e6c40e23099c316b430c

Tx prefix hash: 4cc868c948445780520b115764db3a9a798dea080ad4370bc1d04f2e650febeb
Tx public key: e585a3a00822f9d02e3154df88505dbe9f30913c11a89a411f7afd4039fd882d
Timestamp: 1761463849 Timestamp [UCT]: 2025-10-26 07:30:49 Age [y:d:h:m:s]: 00:025:20:29:51
Block: 1398203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18487 RingCT/type: yes/0
Extra: 01e585a3a00822f9d02e3154df88505dbe9f30913c11a89a411f7afd4039fd882d02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8aa8dbcc77f98bd5e2e51cdce8109014d7778f046378f25c594f9f8a50d41527 0.600000000000 1886496 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": 1398213, "vin": [ { "gen": { "height": 1398203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8aa8dbcc77f98bd5e2e51cdce8109014d7778f046378f25c594f9f8a50d41527" } } ], "extra": [ 1, 229, 133, 163, 160, 8, 34, 249, 208, 46, 49, 84, 223, 136, 80, 93, 190, 159, 48, 145, 60, 17, 168, 154, 65, 31, 122, 253, 64, 57, 253, 136, 45, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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