Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae1e207384f5792cb2f845718a22b0a0a8dc509609589dcb9b2709dc163fe690

Tx prefix hash: f2f1646f47af67a78230c599b73cd58903482a6908b78856c94290a4877c1e6e
Tx public key: 1c1a8d27a1b06c52ee61752fe3cecea6dab1ec7ae55e34a2e737cfabb677dc98
Timestamp: 1696767249 Timestamp [UCT]: 2023-10-08 12:14:09 Age [y:d:h:m:s]: 01:226:05:10:25
Block: 865155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422754 RingCT/type: yes/0
Extra: 011c1a8d27a1b06c52ee61752fe3cecea6dab1ec7ae55e34a2e737cfabb677dc98021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.834415526000 dcy

stealth address amount amount idx
00: 3f2e4869e4b9c0d86b7ce83c595485183e4c10f857b0ab793abbeaa8ea33ea61 0.834415526000 1319681 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": 865165, "vin": [ { "gen": { "height": 865155 } } ], "vout": [ { "amount": 834415526, "target": { "key": "3f2e4869e4b9c0d86b7ce83c595485183e4c10f857b0ab793abbeaa8ea33ea61" } } ], "extra": [ 1, 28, 26, 141, 39, 161, 176, 108, 82, 238, 97, 117, 47, 227, 206, 206, 166, 218, 177, 236, 122, 229, 94, 52, 162, 231, 55, 207, 171, 182, 119, 220, 152, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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