← previous blocknext block →recent activity
Analyzing
Block #99,039,612
16 transactions · 16 stateful · 2026-08-25 12:09:05 UTC
Parallelism
81/100
Blocked
44%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,039,612 · 16 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
1w02w13w16w07w18w010w112w113w215w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2202504e…fad0
0x34b655…2a6f
4 touches
1 conflict
0xb55f6c75…c2d2
0xa6afd3…d132
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xbc2de485…918d
0x34b655…2a6f
4 touches
1 conflict
0xb1856468…e84f
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
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 0x2202504ef1…9ffad0
Audit this contract →
← previous block·next block →recent activity