Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db380d0af3f81c7613e3ee3a8789b25500b9dea7c189c3f50f8cf4e139131745

Tx prefix hash: f5791e2b4287030b66bda0638ce8062b013dd63c7025d6abf02c3a2a46c5c8c3
Tx public key: a20e141c61cf1442cfc6ba75145d417d5be0fca1fb630e2f8fe1a82dd1b2f50a
Timestamp: 1736297802 Timestamp [UCT]: 2025-01-08 00:56:42 Age [y:d:h:m:s]: 00:296:00:32:26
Block: 1192533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209077 RingCT/type: yes/0
Extra: 01a20e141c61cf1442cfc6ba75145d417d5be0fca1fb630e2f8fe1a82dd1b2f50a0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a3da6ff32542788945d5ee4ae327aa696a3f1e8408257064d2a23222f04c1a9 0.600000000000 1679086 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": 1192543, "vin": [ { "gen": { "height": 1192533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a3da6ff32542788945d5ee4ae327aa696a3f1e8408257064d2a23222f04c1a9" } } ], "extra": [ 1, 162, 14, 20, 28, 97, 207, 20, 66, 207, 198, 186, 117, 20, 93, 65, 125, 91, 224, 252, 161, 251, 99, 14, 47, 143, 225, 168, 45, 209, 178, 245, 10, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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