Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08b346a2100fc44664f0ccf366fb6bb948ab023e77120c7a932365ddd4767644

Tx prefix hash: 496d7d324e2d7f2e5b13ead0da623029e10bfdd56f7f2bff46a568d643c14eb5
Tx public key: 1045a722b1e98a5c7af7286f7d2870a790d4fe07fc3c57c6d84aee7c0c896672
Timestamp: 1761192522 Timestamp [UCT]: 2025-10-23 04:08:42 Age [y:d:h:m:s]: 00:020:16:56:31
Block: 1395953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14811 RingCT/type: yes/0
Extra: 011045a722b1e98a5c7af7286f7d2870a790d4fe07fc3c57c6d84aee7c0c89667202110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9ead1984253ca24b680c67a4f28d2f8ee082cfd0455afad93c39595633e9aeb 0.600000000000 1884236 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": 1395963, "vin": [ { "gen": { "height": 1395953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9ead1984253ca24b680c67a4f28d2f8ee082cfd0455afad93c39595633e9aeb" } } ], "extra": [ 1, 16, 69, 167, 34, 177, 233, 138, 92, 122, 247, 40, 111, 125, 40, 112, 167, 144, 212, 254, 7, 252, 60, 87, 198, 216, 74, 238, 124, 12, 137, 102, 114, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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