Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0eab99f2a3ffd0344964b8e55e015f99dde3ba4c768d4b8cf9a6b76488e0ff63

Tx prefix hash: f3277671ba0220ff1d1e7056d65abbed599e00943ffc1e9b73faad0727770622
Tx public key: 6ae7323fea2f8f5ff505e3b6fee964daa6df9f2e93a8aa54807ddc4edf76de98
Timestamp: 1765133942 Timestamp [UCT]: 2025-12-07 18:59:02 Age [y:d:h:m:s]: 00:026:16:37:03
Block: 1428605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19122 RingCT/type: yes/0
Extra: 016ae7323fea2f8f5ff505e3b6fee964daa6df9f2e93a8aa54807ddc4edf76de980211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf5fa5ea4771af6d12314eb770ae83dad5a6d539e2fd5870b5fb4603d8ac94c5 0.600000000000 1917324 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": 1428615, "vin": [ { "gen": { "height": 1428605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf5fa5ea4771af6d12314eb770ae83dad5a6d539e2fd5870b5fb4603d8ac94c5" } } ], "extra": [ 1, 106, 231, 50, 63, 234, 47, 143, 95, 245, 5, 227, 182, 254, 233, 100, 218, 166, 223, 159, 46, 147, 168, 170, 84, 128, 125, 220, 78, 223, 118, 222, 152, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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