Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c1bd317d0a3d4a944a905a65721230c0043da85b4f6abc5386f5f7fe4da2dcd

Tx prefix hash: fc6289230d056f9a51e0505b4e72fda5e5529146d907e440af260fb090224957
Tx public key: 4b996003cc5dca72b3c753811271962c719dcc58f35528b86c5622e60ba2c185
Timestamp: 1702706582 Timestamp [UCT]: 2023-12-16 06:03:02 Age [y:d:h:m:s]: 01:183:10:50:47
Block: 914179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392199 RingCT/type: yes/0
Extra: 014b996003cc5dca72b3c753811271962c719dcc58f35528b86c5622e60ba2c18502110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 293cc8ce5c2ddb9424a7dafbd0c052c764f9c231eaa9ed2da7f3c8c1cad8a071 0.600000000000 1371465 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": 914189, "vin": [ { "gen": { "height": 914179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "293cc8ce5c2ddb9424a7dafbd0c052c764f9c231eaa9ed2da7f3c8c1cad8a071" } } ], "extra": [ 1, 75, 153, 96, 3, 204, 93, 202, 114, 179, 199, 83, 129, 18, 113, 150, 44, 113, 157, 204, 88, 243, 85, 40, 184, 108, 86, 34, 230, 11, 162, 193, 133, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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