← previous blocknext block →recent activity
Analyzing
Block #96,262,134
12 transactions · 8 stateful · 2026-08-15 17:23:15 UTC
Parallelism
83/100
Blocked
13%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,262,134 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49b28397…e3f1
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x05b1b07a…7a99
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
0x34b655…2a6f
2 touches
0 conflicts
0x5e0b8bbe…377b
0x34b655…2a6f
2 touches
0 conflicts
0x69411fb3…e36d
0x34b655…2a6f
2 touches
0 conflicts
0x824b4c5c…a6d0
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x49b283972f…a1e3f1
Audit this contract →
← previous block·next block →recent activity