Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 131638eecbd9f7dcae7cc52956521b26a921c2d623e8398d0f65cfe50f069e79

Tx prefix hash: a761831d2410a053715560cc39d3fef317844c1a2bfcacddc07e2a2c5607aa32
Tx public key: d9fc0af89d31a8377fc42e53ee595082148bcdf4abf005e6c6a6775d074224b2
Timestamp: 1738789447 Timestamp [UCT]: 2025-02-05 21:04:07 Age [y:d:h:m:s]: 00:280:13:15:11
Block: 1212889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198280 RingCT/type: yes/0
Extra: 01d9fc0af89d31a8377fc42e53ee595082148bcdf4abf005e6c6a6775d074224b20211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00a87dd15a22fb0e1b995b3693a520b3d0e4a90717cfea08c278aa25760d938d 0.600000000000 1699664 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": 1212899, "vin": [ { "gen": { "height": 1212889 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00a87dd15a22fb0e1b995b3693a520b3d0e4a90717cfea08c278aa25760d938d" } } ], "extra": [ 1, 217, 252, 10, 248, 157, 49, 168, 55, 127, 196, 46, 83, 238, 89, 80, 130, 20, 139, 205, 244, 171, 240, 5, 230, 198, 166, 119, 93, 7, 66, 36, 178, 2, 17, 0, 0, 0, 2, 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