Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6faa35610d67f65fe7604e32ac33c903de1f793d6ace565972fc60bd650afa9c

Tx prefix hash: 920087da03ba3a49f843890918a6bf8ff1598fac2dab23bc3c21742fe916d2c6
Tx public key: 252f75fd3608f9b6b6fd9f5bd418e7ef629f37b0335a847d64925fd5b96f1d77
Timestamp: 1763690490 Timestamp [UCT]: 2025-11-21 02:01:30 Age [y:d:h:m:s]: 00:032:20:03:05
Block: 1416630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23514 RingCT/type: yes/0
Extra: 01252f75fd3608f9b6b6fd9f5bd418e7ef629f37b0335a847d64925fd5b96f1d770211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd97270f0d89a47220bda2c9d1068bd188fce81b4199f32056cc41f03b47c56f 0.600000000000 1905149 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": 1416640, "vin": [ { "gen": { "height": 1416630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd97270f0d89a47220bda2c9d1068bd188fce81b4199f32056cc41f03b47c56f" } } ], "extra": [ 1, 37, 47, 117, 253, 54, 8, 249, 182, 182, 253, 159, 91, 212, 24, 231, 239, 98, 159, 55, 176, 51, 90, 132, 125, 100, 146, 95, 213, 185, 111, 29, 119, 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