Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa2dc1e980d7a28dc3517df73520ce4debd27d5dfaf4f9b36bdb86d8a0e1feb6

Tx prefix hash: dfaa106faace5495816a74c870cb7b94f9e07222a7cb1d935588514c17fe8d34
Tx public key: 204fe6a1d3fa945c6050590d985dac95567d235ab1f5500859570780e3e5f9ca
Timestamp: 1727937488 Timestamp [UCT]: 2024-10-03 06:38:08 Age [y:d:h:m:s]: 00:191:18:50:35
Block: 1123367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136859 RingCT/type: yes/0
Extra: 01204fe6a1d3fa945c6050590d985dac95567d235ab1f5500859570780e3e5f9ca021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 424aecb72298a0dda5427a2944907ac8c0e68f4c498c4553c0a55acf6b7ff6a6 0.600000000000 1605900 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": 1123377, "vin": [ { "gen": { "height": 1123367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "424aecb72298a0dda5427a2944907ac8c0e68f4c498c4553c0a55acf6b7ff6a6" } } ], "extra": [ 1, 32, 79, 230, 161, 211, 250, 148, 92, 96, 80, 89, 13, 152, 93, 172, 149, 86, 125, 35, 90, 177, 245, 80, 8, 89, 87, 7, 128, 227, 229, 249, 202, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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