← previous blocknext block →recent activity
Analyzing
Block #99,820,952
21 transactions · 20 stateful · 2026-08-28 05:57:29 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,820,952 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w16w08w110w012w115w216w217w320w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a8a0baf…767d
0x34b655…2a6f
6 touches
3 conflicts
0xc852b267…9d14
0x34b655…2a6f
6 touches
3 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0x55208ca9…308d
0x34b655…2a6f
4 touches
1 conflict
0x55836904…a6fe
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
3 conflicts on slot 0x2a8a0baf5d…0b767d
Audit this contract →
← previous block·next block →recent activity