Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26947abe9e5a12d5cbb40f2c386778f32dc67f7b92b15937bb71b28ca7040a16

Tx prefix hash: 1117c8ea9ea46ea3c30f3c3dd5c7efc71a644637c6b283ecfa171834923b185b
Tx public key: 57e8d215c1ab05c3962bfcbd901124ecf410fa172ce1cac221dc7c281f516890
Timestamp: 1722511626 Timestamp [UCT]: 2024-08-01 11:27:06 Age [y:d:h:m:s]: 01:099:20:00:03
Block: 1078377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329836 RingCT/type: yes/0
Extra: 0157e8d215c1ab05c3962bfcbd901124ecf410fa172ce1cac221dc7c281f516890021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0842d2a84ab71259256770b3461f1876c2b57157a6f9482eb3fab7b69dd944b 0.600000000000 1550954 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": 1078387, "vin": [ { "gen": { "height": 1078377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0842d2a84ab71259256770b3461f1876c2b57157a6f9482eb3fab7b69dd944b" } } ], "extra": [ 1, 87, 232, 210, 21, 193, 171, 5, 195, 150, 43, 252, 189, 144, 17, 36, 236, 244, 16, 250, 23, 44, 225, 202, 194, 33, 220, 124, 40, 31, 81, 104, 144, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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