← previous blocknext block →recent activity
Analyzing
Block #99,091,678
12 transactions · 11 stateful · 2026-08-25 16:34:28 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,091,678 · 12 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
1w02w13w06w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0xb856d1a1…1f18
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x0d03bddb…6658
0x34b655…2a6f
2 touches
0 conflicts
0x1c2f0c4c…9bca
0x34b655…2a6f
2 touches
0 conflicts
0x378a2c05…5587
0x34b655…2a6f
2 touches
0 conflicts
0x3d1a888b…ba9d
0x34b655…2a6f
2 touches
0 conflicts
0x67dc9ab6…e344
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 0x6d1b72eefe…416b78
Audit this contract →
← previous block·next block →recent activity