← previous blocknext block →recent activity
Analyzing
Block #99,979,879
22 transactions · 22 stateful · 2026-08-28 19:19:01 UTC
Parallelism
77/100
Blocked
41%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,979,879 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w08w09w110w211w315w118w419w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd13df66…0029
0x34b655…2a6f
10 touches
10 conflicts
0xa9a9d0e0…4087
0x34b655…2a6f
8 touches
6 conflicts
0x731d7308…fd26
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xf61165ef…adb9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x96a08475…54fe
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
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
10 conflicts on slot 0xfd13df6606…a60029
Audit this contract →
← previous block·next block →recent activity