← previous blocknext block →recent activity
Analyzing
Block #99,820,389
11 transactions · 11 stateful · 2026-08-28 05:54:39 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,820,389 · 11 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
1w02w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x49f39582…ccc7
0x754704…b603
4 touches
1 conflict
0xad47b33d…500b
0x754704…b603
4 touches
1 conflict
0xf00d2133…d68e
0x754704…b603
4 touches
1 conflict
0x48961b46…3dad
0x99c7a7…8bf0
4 touches
1 conflict
0xa1ac5a56…17d8
0x99c7a7…8bf0
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x2f4b2cf9…4e1e
0x2b46c0…1669
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 0x261cbea79d…12e35e
Audit this contract →
← previous block·next block →recent activity