Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d889452c9963a7394d0643278cf2ba51c46c5eb7594c8f73590c051b92e35368

Tx prefix hash: 900e972c0913c31b6b7d9b68c9a2861fa057d859a39685c9152e4f367a714f94
Tx public key: 8c9f9c83e9b14d904414cc7f4f5346c3ca40904106e64e72d12cf000afcf13f3
Timestamp: 1736205615 Timestamp [UCT]: 2025-01-06 23:20:15 Age [y:d:h:m:s]: 00:309:20:30:16
Block: 1191763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218967 RingCT/type: yes/0
Extra: 018c9f9c83e9b14d904414cc7f4f5346c3ca40904106e64e72d12cf000afcf13f30211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbef8a78cc6457da89e4f9df5808178c06133d30206914eb07ee08e4f14699e3 0.600000000000 1678304 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": 1191773, "vin": [ { "gen": { "height": 1191763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbef8a78cc6457da89e4f9df5808178c06133d30206914eb07ee08e4f14699e3" } } ], "extra": [ 1, 140, 159, 156, 131, 233, 177, 77, 144, 68, 20, 204, 127, 79, 83, 70, 195, 202, 64, 144, 65, 6, 230, 78, 114, 209, 44, 240, 0, 175, 207, 19, 243, 2, 17, 0, 0, 0, 9, 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