Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21d37b332edca5ea4cd85de43c1dc9f6e545faffe223ae59fa9ce5f684332e2b

Tx prefix hash: 979eff30d08e9eefa968b71d7857ed9cdecf92097d509bb372aac7a88676b8ad
Tx public key: 80cda2ade7aaa9ed4d75a635b01bef42664f7d7ed7c63484e7c62d9c14be7fbb
Timestamp: 1733959834 Timestamp [UCT]: 2024-12-11 23:30:34 Age [y:d:h:m:s]: 00:110:09:46:32
Block: 1173205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78671 RingCT/type: yes/0
Extra: 0180cda2ade7aaa9ed4d75a635b01bef42664f7d7ed7c63484e7c62d9c14be7fbb021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a73d8c5d35d259644a79c0f00282ed8011036dda2f25a6c501938f54b40c1fe2 0.600000000000 1659200 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": 1173215, "vin": [ { "gen": { "height": 1173205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a73d8c5d35d259644a79c0f00282ed8011036dda2f25a6c501938f54b40c1fe2" } } ], "extra": [ 1, 128, 205, 162, 173, 231, 170, 169, 237, 77, 117, 166, 53, 176, 27, 239, 66, 102, 79, 125, 126, 215, 198, 52, 132, 231, 198, 45, 156, 20, 190, 127, 187, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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