Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e758e914f9b10d5b83e6c14c0d7dc3e6c0208d3f355fde0011de88617d8091e8

Tx prefix hash: b428c9bc862a604a4c0232e6b9f54f88416e3d91a5432d57c55501f1503c6805
Tx public key: bfc9fadc3b2d592d1978b23893d7f858a4e042585a2a135da0d0765412c0c293
Timestamp: 1718211612 Timestamp [UCT]: 2024-06-12 17:00:12 Age [y:d:h:m:s]: 00:277:19:43:00
Block: 1042731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198546 RingCT/type: yes/0
Extra: 01bfc9fadc3b2d592d1978b23893d7f858a4e042585a2a135da0d0765412c0c2930211000000018fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d107bd477b5bbd4dc520ccff7c55f3e4166a9866aa6f8cd7e0d75caabafe0c02 0.600000000000 1511718 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": 1042741, "vin": [ { "gen": { "height": 1042731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d107bd477b5bbd4dc520ccff7c55f3e4166a9866aa6f8cd7e0d75caabafe0c02" } } ], "extra": [ 1, 191, 201, 250, 220, 59, 45, 89, 45, 25, 120, 178, 56, 147, 215, 248, 88, 164, 224, 66, 88, 90, 42, 19, 93, 160, 208, 118, 84, 18, 192, 194, 147, 2, 17, 0, 0, 0, 1, 143, 218, 155, 45, 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