Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b58b94c5b81aca0881fa521599f06c16a447162be7313bd1eb00d00777038f3

Tx prefix hash: 433145b120dae6c504da19fdfd51555162e50574cc62aa4f9ca9eb8379092ee3
Tx public key: f61aa0afb0606599b36e875ea3ded1913f350f3fe17a28ff54c81a1c4f73416d
Timestamp: 1696813060 Timestamp [UCT]: 2023-10-09 00:57:40 Age [y:d:h:m:s]: 01:200:19:48:49
Block: 865539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404572 RingCT/type: yes/0
Extra: 01f61aa0afb0606599b36e875ea3ded1913f350f3fe17a28ff54c81a1c4f73416d021100000004faf35c9c000000000000000000

1 output(s) for total of 0.831974518000 dcy

stealth address amount amount idx
00: 6cd86c49445ea78b852e458c7e59df2767a06a0dd18f2b583086bf8714477c4e 0.831974518000 1320075 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": 865549, "vin": [ { "gen": { "height": 865539 } } ], "vout": [ { "amount": 831974518, "target": { "key": "6cd86c49445ea78b852e458c7e59df2767a06a0dd18f2b583086bf8714477c4e" } } ], "extra": [ 1, 246, 26, 160, 175, 176, 96, 101, 153, 179, 110, 135, 94, 163, 222, 209, 145, 63, 53, 15, 63, 225, 122, 40, 255, 84, 200, 26, 28, 79, 115, 65, 109, 2, 17, 0, 0, 0, 4, 250, 243, 92, 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