Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b80b537ecc33555ed91aecd1f048a1b5e47d20ab015de78f2a84009c76b950c2

Tx prefix hash: 8e17bb579ea37f5559de2168693b23d933ef200ba3230b245f66bd73501245dc
Tx public key: 82962401efa4cd84be2d1c801ab3b1b4c0a8d74cfa2826a6ec6525f6a0850e78
Timestamp: 1723984158 Timestamp [UCT]: 2024-08-18 12:29:18 Age [y:d:h:m:s]: 01:138:00:22:26
Block: 1090588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357170 RingCT/type: yes/0
Extra: 0182962401efa4cd84be2d1c801ab3b1b4c0a8d74cfa2826a6ec6525f6a0850e7802110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef04a0ab86c0d6159876d0497979802393d9f77107129909cb4aca0a9940adee 0.600000000000 1565211 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": 1090598, "vin": [ { "gen": { "height": 1090588 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef04a0ab86c0d6159876d0497979802393d9f77107129909cb4aca0a9940adee" } } ], "extra": [ 1, 130, 150, 36, 1, 239, 164, 205, 132, 190, 45, 28, 128, 26, 179, 177, 180, 192, 168, 215, 76, 250, 40, 38, 166, 236, 101, 37, 246, 160, 133, 14, 120, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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