← previous blocknext block →recent activity
Analyzing
Block #96,638,533
14 transactions · 14 stateful · 2026-08-17 00:56:40 UTC
Parallelism
86/100
Blocked
7%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,638,533 · 14 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
5w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c0e49c9…7833
0x34b655…2a6f
4 touches
1 conflict
0x4bdb07b7…9d1b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0fb4d66e…8f33
0x34b655…2a6f
2 touches
0 conflicts
0x126a0344…4465
0x34b655…2a6f
2 touches
0 conflicts
0x177f744d…b7dd
0x34b655…2a6f
2 touches
0 conflicts
0x1c3f9951…ff99
0x34b655…2a6f
2 touches
0 conflicts
0x75f108dc…f5a7
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 0x3c0e49c972…657833
Audit this contract →
← previous block·next block →recent activity