Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95b7a5ab3157311c36c5c0c9f74b732c7189dad25696ab5f20f89a824e58e0b7

Tx prefix hash: b4e76fcd1273b6597c1b492f710e2233017071c6b65e86ec64f6ec236cd85da7
Tx public key: e600a6d7b3e42e09f742b403104fd6f72a49b4d0b01e2c45f1f8a7cc50c2d5ef
Timestamp: 1745312057 Timestamp [UCT]: 2025-04-22 08:54:17 Age [y:d:h:m:s]: 00:213:14:17:58
Block: 1266889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150379 RingCT/type: yes/0
Extra: 01e600a6d7b3e42e09f742b403104fd6f72a49b4d0b01e2c45f1f8a7cc50c2d5ef021100000008dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0435c90d6343f1df28966cc5665aab92fcbaa99bb8201f0a1415690e73e1da39 0.600000000000 1754114 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": 1266899, "vin": [ { "gen": { "height": 1266889 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0435c90d6343f1df28966cc5665aab92fcbaa99bb8201f0a1415690e73e1da39" } } ], "extra": [ 1, 230, 0, 166, 215, 179, 228, 46, 9, 247, 66, 180, 3, 16, 79, 214, 247, 42, 73, 180, 208, 176, 30, 44, 69, 241, 248, 167, 204, 80, 194, 213, 239, 2, 17, 0, 0, 0, 8, 219, 181, 113, 193, 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