Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6968b709217e896488e57c5b69d162005492a513e800579c2005adaba70633ec

Tx prefix hash: e62364f2bf15fb3d4e2659f8f74f1f77c298c2f690d18bdc09cbc1b65d460487
Tx public key: 7096c14ec9c113eab2a2c1fa8c15e57b946ee77aa1b195142f753edcc721b56b
Timestamp: 1704380690 Timestamp [UCT]: 2024-01-04 15:04:50 Age [y:d:h:m:s]: 01:098:04:28:16
Block: 928068 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331279 RingCT/type: yes/0
Extra: 017096c14ec9c113eab2a2c1fa8c15e57b946ee77aa1b195142f753edcc721b56b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2c1d72303bd46df8837dc69c6dc08056a3ef539fc8b0bd80225abc0de5f682b 0.600000000000 1385924 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": 928078, "vin": [ { "gen": { "height": 928068 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2c1d72303bd46df8837dc69c6dc08056a3ef539fc8b0bd80225abc0de5f682b" } } ], "extra": [ 1, 112, 150, 193, 78, 201, 193, 19, 234, 178, 162, 193, 250, 140, 21, 229, 123, 148, 110, 231, 122, 161, 177, 149, 20, 47, 117, 62, 220, 199, 33, 181, 107, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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