← previous blocknext block →recent activity
Analyzing
Block #96,017,618
8 transactions · 7 stateful · 2026-08-14 20:53:21 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,017,618 · 8 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x349f436e…80e6
0x34b655…2a6f
4 touches
1 conflict
0xcd5c0ecb…4b5f
0x34b655…2a6f
4 touches
1 conflict
0xa47b7766…ee6e
0x34b655…2a6f
4 touches
1 conflict
0xc9c2f132…25f2
0x34b655…2a6f
4 touches
1 conflict
0x57330c5d…9973
0x34b655…2a6f
2 touches
0 conflicts
0x68c07cb9…ae14
0x34b655…2a6f
2 touches
0 conflicts
0x9fd37234…2731
0x34b655…2a6f
2 touches
0 conflicts
0xb062639b…1851
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 0x349f436e90…2b80e6
Audit this contract →
← previous block·next block →recent activity