← previous blocknext block →recent activity
Analyzing
Block #99,744,777
13 transactions · 13 stateful · 2026-08-27 23:31:15 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,744,777 · 13 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
1w02w14w05w16w27w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb76e6acb…2af7
0x34b655…2a6f
6 touches
3 conflicts
0xba9f88e8…9c33
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…153c
0x34b655…2a6f
6 touches
3 conflicts
0x1aa85bda…e324
0x34b655…2a6f
6 touches
3 conflicts
0x7a1531cd…7319
0x34b655…2a6f
6 touches
3 conflicts
0x5164ab0e…01e1
0xc8689a…ee79
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 0xb76e6acb5c…2a2af7
Audit this contract →
← previous block·next block →recent activity