Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6afe1aa0f704dd57c32b4f66eaca8829db1b9b7c70571b129d5cb75e742994e

Tx prefix hash: a6ab77bdc1d0678eee2efa723ddb9629916a7749f333d00a56e8768fda1d4a1b
Tx public key: ab0b6318ddd021bf2e887d46cc9c988e53bb3c07bae0d3e4a9a8b73ea2efa1f8
Timestamp: 1705769517 Timestamp [UCT]: 2024-01-20 16:51:57 Age [y:d:h:m:s]: 01:148:21:35:15
Block: 939552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367456 RingCT/type: yes/0
Extra: 01ab0b6318ddd021bf2e887d46cc9c988e53bb3c07bae0d3e4a9a8b73ea2efa1f802110000001359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6dd8175389d5500cdebc2708cad1799bca5ba3b8c6b0cf68959fbe1ebdac1305 0.600000000000 1397660 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": 939562, "vin": [ { "gen": { "height": 939552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6dd8175389d5500cdebc2708cad1799bca5ba3b8c6b0cf68959fbe1ebdac1305" } } ], "extra": [ 1, 171, 11, 99, 24, 221, 208, 33, 191, 46, 136, 125, 70, 204, 156, 152, 142, 83, 187, 60, 7, 186, 224, 211, 228, 169, 168, 183, 62, 162, 239, 161, 248, 2, 17, 0, 0, 0, 19, 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