Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26ffb4acaf7d9a376126492bd065fae80ab6bb70a07982dfebc9429fdc0a03d5

Tx prefix hash: 3c6c97353e4d7b70827bbd4312a56bb4c3f7e649046430c3bb741933fc77a2a3
Tx public key: 6f5a4f95d717fd43d94373d29a2bf0f4f9c6a5be2b210ad1f752ee44fe3ac3a5
Timestamp: 1702155898 Timestamp [UCT]: 2023-12-09 21:04:58 Age [y:d:h:m:s]: 01:333:02:59:25
Block: 909623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496932 RingCT/type: yes/0
Extra: 016f5a4f95d717fd43d94373d29a2bf0f4f9c6a5be2b210ad1f752ee44fe3ac3a50211000000044b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 182fac8b9239948ff64271b6d7d8da92504b7827b4521a67826f27839c55bd16 0.600000000000 1366724 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": 909633, "vin": [ { "gen": { "height": 909623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "182fac8b9239948ff64271b6d7d8da92504b7827b4521a67826f27839c55bd16" } } ], "extra": [ 1, 111, 90, 79, 149, 215, 23, 253, 67, 217, 67, 115, 210, 154, 43, 240, 244, 249, 198, 165, 190, 43, 33, 10, 209, 247, 82, 238, 68, 254, 58, 195, 165, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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