← previous blocknext block →recent activity
Analyzing
Block #96,683,096
13 transactions · 10 stateful · 2026-08-17 04:40:47 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,683,096 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c619b7d…f4fa
0x34b655…2a6f
6 touches
3 conflicts
0xefb805bc…0d8d
0x34b655…2a6f
4 touches
1 conflict
0x266a6b2c…4376
0x34b655…2a6f
4 touches
1 conflict
0x266a6b2c…4377
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc22a0c80…6c90
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
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
3 conflicts on slot 0x4c619b7d61…22f4fa
Audit this contract →
← previous block·next block →recent activity