← previous blocknext block →recent activity
Analyzing
Block #99,791,264
15 transactions · 15 stateful · 2026-08-28 03:27:17 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,791,264 · 15 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
6w08w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe38f109…09d1
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xdd9dc4b3…73b8
0x34b655…2a6f
4 touches
1 conflict
0x6d6c44e2…8f45
0x34b655…2a6f
3 touches
1 conflict
0x5a7e4e98…1f3b
0x754704…b603
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 0xbe38f109ec…e609d1
Audit this contract →
← previous block·next block →recent activity