← previous blocknext block →recent activity
Analyzing
Block #96,208,244
4 transactions · 3 stateful · 2026-08-15 12:52:12 UTC
Parallelism
50/100
Blocked
33%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,208,244 · 4 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x8ad1e6cf…074c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0661e5b9…8a09
0x34b655…2a6f
2 touches
0 conflicts
0x0cc3cf17…3841
0x34b655…2a6f
2 touches
0 conflicts
0x3a28ef0b…e875
0x34b655…2a6f
2 touches
0 conflicts
0x3a28ef0b…e876
0x34b655…2a6f
2 touches
0 conflicts
0x3ab86b5a…8290
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity