← previous blocknext block →recent activity
Analyzing
Block #96,638,671
13 transactions · 13 stateful · 2026-08-17 00:57:22 UTC
Parallelism
62/100
Blocked
46%
Avg conflicts / tx
1.31
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,638,671 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w26w37w110w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f69fba7…a65a
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
6 touches
3 conflicts
0xa6bb12cd…bf4a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x8d175439…fb79
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x0f69fba799…eea65a
Audit this contract →
← previous block·next block →recent activity