Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aec6cc349d48d6fa34f8fd0535e87ec73fa141c6f3d180c6ef6a0b96013e916e

Tx prefix hash: d8542b01e3a92bb93c4aa9d17fcd141ed048456d28166610106a7643a3b17157
Tx public key: 6a499001b7621e8a083a2a33662a8e56a265e936d500d3a0b3c7932b7bf45d78
Timestamp: 1678900573 Timestamp [UCT]: 2023-03-15 17:16:13 Age [y:d:h:m:s]: 01:311:00:38:26
Block: 717710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 483164 RingCT/type: yes/0
Extra: 016a499001b7621e8a083a2a33662a8e56a265e936d500d3a0b3c7932b7bf45d780211000000015029cbac000000000000000000

1 output(s) for total of 2.569973953000 dcy

stealth address amount amount idx
00: a288e9099ce02a8ce03d98496f4860304d6fa02f40b10ca0ef1f839639913577 2.569973953000 1162321 of 0

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": 717720, "vin": [ { "gen": { "height": 717710 } } ], "vout": [ { "amount": 2569973953, "target": { "key": "a288e9099ce02a8ce03d98496f4860304d6fa02f40b10ca0ef1f839639913577" } } ], "extra": [ 1, 106, 73, 144, 1, 183, 98, 30, 138, 8, 58, 42, 51, 102, 42, 142, 86, 162, 101, 233, 54, 213, 0, 211, 160, 179, 199, 147, 43, 123, 244, 93, 120, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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