← previous blocknext block →recent activity
Analyzing
Block #95,654,026
33 transactions · 30 stateful · 2026-08-13 14:23:04 UTC
Parallelism
76/100
Blocked
60%
Avg conflicts / tx
1.7
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #95,654,026 · 33 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w16w27w38w420w423w124w625w732w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0031
0x59df86…2780
12 touches
15 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x071f030f…1797
0x34b655…2a6f
6 touches
3 conflicts
0x6d148b57…bc8f
0x34b655…2a6f
6 touches
3 conflicts
0xcef70a96…db44
0x34b655…2a6f
6 touches
3 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
21 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity