Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3c83768f938ee687bdb52f3c203d78b46b1ece02ed1fe756e531f68c5965e3b

Tx prefix hash: cd3d2e33f9d41ebcc4647fef8ae692cb2e97ecab631de780fa3140987ba92bd9
Tx public key: a13f0d7428d780723f10c7673ee093c0b3c3aaa2fdacdb3de92053d16393ebd2
Timestamp: 1732163798 Timestamp [UCT]: 2024-11-21 04:36:38 Age [y:d:h:m:s]: 00:121:05:45:01
Block: 1158296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86475 RingCT/type: yes/0
Extra: 01a13f0d7428d780723f10c7673ee093c0b3c3aaa2fdacdb3de92053d16393ebd20211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef66f2da914770627b03a3e3323bc547ac28af6cd42c6b76584fb366dc992d6d 0.600000000000 1643925 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": 1158306, "vin": [ { "gen": { "height": 1158296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef66f2da914770627b03a3e3323bc547ac28af6cd42c6b76584fb366dc992d6d" } } ], "extra": [ 1, 161, 63, 13, 116, 40, 215, 128, 114, 63, 16, 199, 103, 62, 224, 147, 192, 179, 195, 170, 162, 253, 172, 219, 61, 233, 32, 83, 209, 99, 147, 235, 210, 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