← previous blocknext block →recent activity
Analyzing
Block #99,263,532
16 transactions · 16 stateful · 2026-08-26 06:59:19 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,263,532 · 16 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
10w012w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x310a7246…2dcb
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfc8d572c…b27d
0x34b655…2a6f
4 touches
1 conflict
0x23255d8b…c5fd
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x6419eb11…3680
0x34b655…2a6f
2 touches
0 conflicts
0x9a100e05…c541
0x34b655…2a6f
2 touches
0 conflicts
0xab62f0aa…10de
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 0x310a7246ab…012dcb
Audit this contract →
← previous block·next block →recent activity