Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d4a79d413c8cb03ef1347a1aa2078ccb8a24bd101e8a9ec11bd425ce1f087db

Tx prefix hash: de870ab8ed4474e603029746e8a6f4af3da9f10ffb710a006522a3326bd1217e
Tx public key: 00ac9676e5aef34affa2a3625f268b4d7a1edf20b62dcf1facc0b6682ac8fafc
Timestamp: 1736541780 Timestamp [UCT]: 2025-01-10 20:43:00 Age [y:d:h:m:s]: 00:079:14:16:02
Block: 1194556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56664 RingCT/type: yes/0
Extra: 0100ac9676e5aef34affa2a3625f268b4d7a1edf20b62dcf1facc0b6682ac8fafc021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b36bf875631fe3f082a68591939821afb242519e32dcdce3ff2f08fb96b7281e 0.600000000000 1681131 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": 1194566, "vin": [ { "gen": { "height": 1194556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b36bf875631fe3f082a68591939821afb242519e32dcdce3ff2f08fb96b7281e" } } ], "extra": [ 1, 0, 172, 150, 118, 229, 174, 243, 74, 255, 162, 163, 98, 95, 38, 139, 77, 122, 30, 223, 32, 182, 45, 207, 31, 172, 192, 182, 104, 42, 200, 250, 252, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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