← previous blocknext block →recent activity
Analyzing
Block #96,544,142
7 transactions · 6 stateful · 2026-08-16 17:01:55 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,544,142 · 7 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
1w02w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17f5dec8…3332
0x34b655…2a6f
4 touches
1 conflict
0x21280422…0930
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x07d94be1…7fa8
0x34b655…2a6f
2 touches
0 conflicts
0x0b00aeff…7bd3
0x34b655…2a6f
2 touches
0 conflicts
0x1c097b81…0164
0x34b655…2a6f
2 touches
0 conflicts
0x1c097b81…0165
0x34b655…2a6f
2 touches
0 conflicts
0x39423b28…1e57
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 0x17f5dec852…2f3332
Audit this contract →
← previous block·next block →recent activity