← previous blocknext block →recent activity
Analyzing
Block #96,143,211
13 transactions · 9 stateful · 2026-08-15 07:25:07 UTC
Parallelism
77/100
Blocked
44%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,143,211 · 13 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
1w02w17w08w110w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea1b8c07…b969
0x34b655…2a6f
4 touches
1 conflict
0x8ae3e2cf…d1a9
0x34b655…2a6f
4 touches
1 conflict
0xb0cc22f4…af33
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x5c23b2b4…ea22
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0003
0x04ddf6…7f33
2 touches
0 conflicts
0xaeabffea…5dd4
0x0a3323…0a3c
2 touches
0 conflicts
0xb1632c2f…d991
0x0a3323…0a3c
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 0xea1b8c07ee…d0b969
Audit this contract →
← previous block·next block →recent activity