Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bb61f6313e49cc193cbb35b41985c900dfc5858fa1b990766e2fe89b3a9fe8a

Tx prefix hash: 0a64d2e5fa1ad2b6d51330d4bb7eba1bec8b72aeb113e8ba590cdb3557e6d696
Tx public key: f2bddfe91928595e43b4f7cdcf107229e9392184c3555adf627f14bf8e7b3c87
Timestamp: 1745188159 Timestamp [UCT]: 2025-04-20 22:29:19 Age [y:d:h:m:s]: 00:214:09:15:31
Block: 1265851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150948 RingCT/type: yes/0
Extra: 01f2bddfe91928595e43b4f7cdcf107229e9392184c3555adf627f14bf8e7b3c87021100000004dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53432aea9738238e9379c30f9b74525c58a8efd4cd78d905054fa9f61c8a3f55 0.600000000000 1753064 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": 1265861, "vin": [ { "gen": { "height": 1265851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53432aea9738238e9379c30f9b74525c58a8efd4cd78d905054fa9f61c8a3f55" } } ], "extra": [ 1, 242, 189, 223, 233, 25, 40, 89, 94, 67, 180, 247, 205, 207, 16, 114, 41, 233, 57, 33, 132, 195, 85, 90, 223, 98, 127, 20, 191, 142, 123, 60, 135, 2, 17, 0, 0, 0, 4, 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