← previous blocknext block →recent activity
Analyzing
Block #99,284,866
11 transactions · 11 stateful · 2026-08-26 08:46:37 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,284,866 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3307b57f…060a
0x34b655…2a6f
4 touches
1 conflict
0x74ca933a…1a22
0x34b655…2a6f
4 touches
1 conflict
0xb550abea…2729
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xdd355a8e…ea72
0x34b655…2a6f
4 touches
1 conflict
0x171d9a84…b3b7
0x34b655…2a6f
2 touches
0 conflicts
0x1ecde9da…3735
0x34b655…2a6f
2 touches
0 conflicts
0x49509e76…cd79
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 0x3307b57f9d…6e060a
Audit this contract →
← previous block·next block →recent activity