Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5a2b17f9dca7f4a632e4feee6301783bafe76934967899f9f9eca842b54e8d3

Tx prefix hash: 54cad135af1e6fd042085c8799eb21bcd4d0d3278d422fb13a2223849d5d77b6
Tx public key: d5c76b4a3950e8f33beb2bf2693138a6f010c99fdbe8dfdb792717e87d58e993
Timestamp: 1680364056 Timestamp [UCT]: 2023-04-01 15:47:36 Age [y:d:h:m:s]: 02:005:20:08:07
Block: 729856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 525679 RingCT/type: yes/0
Extra: 01d5c76b4a3950e8f33beb2bf2693138a6f010c99fdbe8dfdb792717e87d58e993021100000002e6d27f9c000000000000000000

1 output(s) for total of 2.342525499000 dcy

stealth address amount amount idx
00: f5caea9f16f8fe1f1c815772d3300b54089d8858e8eee33cd1276e7add2f619b 2.342525499000 1175425 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": 729866, "vin": [ { "gen": { "height": 729856 } } ], "vout": [ { "amount": 2342525499, "target": { "key": "f5caea9f16f8fe1f1c815772d3300b54089d8858e8eee33cd1276e7add2f619b" } } ], "extra": [ 1, 213, 199, 107, 74, 57, 80, 232, 243, 59, 235, 43, 242, 105, 49, 56, 166, 240, 16, 201, 159, 219, 232, 223, 219, 121, 39, 23, 232, 125, 88, 233, 147, 2, 17, 0, 0, 0, 2, 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