Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 105a11827c64c3ff969e67779ada80c8191a4379381eabed04ac0c2edef4d3c2

Tx prefix hash: 9579445fd67c444b28e198be331ca9ac84af7cbf68df4c4728b5c4e76ca5d08c
Tx public key: 9edf68f27a2acf6f0a549f567c073258683c271f59501d7f403dc28a34ab3a87
Timestamp: 1702982619 Timestamp [UCT]: 2023-12-19 10:43:39 Age [y:d:h:m:s]: 01:324:23:19:24
Block: 916479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 491100 RingCT/type: yes/0
Extra: 019edf68f27a2acf6f0a549f567c073258683c271f59501d7f403dc28a34ab3a87021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46c2be759fdf5428ca77f005352d5ab5cc2a4fa46836f740a7c09785f072ae2e 0.600000000000 1374031 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": 916489, "vin": [ { "gen": { "height": 916479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46c2be759fdf5428ca77f005352d5ab5cc2a4fa46836f740a7c09785f072ae2e" } } ], "extra": [ 1, 158, 223, 104, 242, 122, 42, 207, 111, 10, 84, 159, 86, 124, 7, 50, 88, 104, 60, 39, 31, 89, 80, 29, 127, 64, 61, 194, 138, 52, 171, 58, 135, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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