← previous blocknext block →recent activity
Analyzing
Block #97,196,203
19 transactions · 12 stateful · 2026-08-18 23:54:45 UTC
Parallelism
89/100
Blocked
8%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,196,203 · 19 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
4w05w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x496ff651…1310
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
2 touches
0 conflicts
0x1f08873e…f596
0x34b655…2a6f
2 touches
0 conflicts
0x48a0f121…953b
0x34b655…2a6f
2 touches
0 conflicts
0x52f2b639…423f
0x34b655…2a6f
2 touches
0 conflicts
0x6c2f6464…6a7e
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 0x496ff65132…401310
Audit this contract →
← previous block·next block →recent activity