Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a10c1b2d57fc2549b92fe3765d8c152a7080d15d33a1b7ab87d611fcb923204

Tx prefix hash: e0693fe8afb1752af77b378d513ace6fcc2663b464eabeaf42c872847a04abb4
Tx public key: 451a0276b07d8e2723d323bd6394c1d2ab61b682bf5ffd31c6f4ab897335f7e5
Timestamp: 1725593762 Timestamp [UCT]: 2024-09-06 03:36:02 Age [y:d:h:m:s]: 00:218:06:42:52
Block: 1103929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155849 RingCT/type: yes/0
Extra: 01451a0276b07d8e2723d323bd6394c1d2ab61b682bf5ffd31c6f4ab897335f7e5021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1917a6702c3801a7e9e61fca6a3642d24267c669b42edfa11cbdcf40d2a016d 0.600000000000 1580948 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": 1103939, "vin": [ { "gen": { "height": 1103929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1917a6702c3801a7e9e61fca6a3642d24267c669b42edfa11cbdcf40d2a016d" } } ], "extra": [ 1, 69, 26, 2, 118, 176, 125, 142, 39, 35, 211, 35, 189, 99, 148, 193, 210, 171, 97, 182, 130, 191, 95, 253, 49, 198, 244, 171, 137, 115, 53, 247, 229, 2, 17, 0, 0, 0, 4, 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