← previous blocknext block →recent activity
Analyzing
Block #99,250,794
13 transactions · 13 stateful · 2026-08-26 05:55:08 UTC
Parallelism
85/100
Blocked
15%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,250,794 · 13 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
1w02w16w011w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x168f75b5…b2d1
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x2202504e…fad0
0x34b655…2a6f
2 touches
0 conflicts
0x2860b9bb…282c
0x34b655…2a6f
2 touches
0 conflicts
0x65192461…1a47
0x34b655…2a6f
2 touches
0 conflicts
0x67b854bc…bc4d
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 0x4c29ecd55a…1058b6
Audit this contract →
← previous block·next block →recent activity