Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 796a4c571f039ebb873891a01dd3c5507d51a8b1b7c8f51f31bdaad42e513aff

Tx prefix hash: e8212f1c6763b22ac217b03608aa992a8fdd4afbdf1be84f6b1ce33b95b36078
Tx public key: 2eaa7cee23fcf614001521e31cdde584fc6d9a19f6cac79b814cc7e44ebfbf46
Timestamp: 1731062789 Timestamp [UCT]: 2024-11-08 10:46:29 Age [y:d:h:m:s]: 00:215:14:49:22
Block: 1149185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153944 RingCT/type: yes/0
Extra: 012eaa7cee23fcf614001521e31cdde584fc6d9a19f6cac79b814cc7e44ebfbf460211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b789c30134954b4ae7a64465ec592da79673f0e3ec528ed112a7c40fa0dffc09 0.600000000000 1634212 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": 1149195, "vin": [ { "gen": { "height": 1149185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b789c30134954b4ae7a64465ec592da79673f0e3ec528ed112a7c40fa0dffc09" } } ], "extra": [ 1, 46, 170, 124, 238, 35, 252, 246, 20, 0, 21, 33, 227, 28, 221, 229, 132, 252, 109, 154, 25, 246, 202, 199, 155, 129, 76, 199, 228, 78, 191, 191, 70, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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