Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd16e58fc8e208f5eac8948fa6b188d60c5cd33ec481741143d4e71419f46623

Tx prefix hash: 74eb872543683393687df6442c4a3b7f9e63e2f9bd76c5c4951191b4ee95a9d4
Tx public key: 6d40a2e105131145819f783fb37c7e7fc90dee279b490f51581fc9e09013f8a5
Timestamp: 1705250614 Timestamp [UCT]: 2024-01-14 16:43:34 Age [y:d:h:m:s]: 01:093:14:52:56
Block: 935270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328000 RingCT/type: yes/0
Extra: 016d40a2e105131145819f783fb37c7e7fc90dee279b490f51581fc9e09013f8a502110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2eb0ef59c7cbc20d9c0c3bd60a2026187acf60ba0c52b947925d545053f98f2b 0.600000000000 1393286 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": 935280, "vin": [ { "gen": { "height": 935270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2eb0ef59c7cbc20d9c0c3bd60a2026187acf60ba0c52b947925d545053f98f2b" } } ], "extra": [ 1, 109, 64, 162, 225, 5, 19, 17, 69, 129, 159, 120, 63, 179, 124, 126, 127, 201, 13, 238, 39, 155, 73, 15, 81, 88, 31, 201, 224, 144, 19, 248, 165, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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