← previous blocknext block →recent activity
Analyzing
Block #96,142,132
11 transactions · 10 stateful · 2026-08-15 07:19:42 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,142,132 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w17w28w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0cc22f4…af33
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x750fb05c…0e99
0x34b655…2a6f
4 touches
1 conflict
0x3111a64f…eb7f
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x5e8ddd73…4dfb
0x34b655…2a6f
4 touches
1 conflict
0x9b36f19f…fa5a
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 0xb0cc22f4c2…33af33
Audit this contract →
← previous block·next block →recent activity