← previous blocknext block →recent activity
Analyzing
Block #99,937,480
27 transactions · 20 stateful · 2026-08-28 15:45:24 UTC
Parallelism
85/100
Blocked
50%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,937,480 · 27 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
1w03w16w07w08w110w112w213w116w217w321w223w324w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xaa894c29…6e88
0xd32edf…ff58
5 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xa4e3b3b1…0911
0x2a68ba…90c5
4 touches
1 conflict
0xd6bd849a…5597
0x2a68ba…90c5
4 touches
1 conflict
0xeba56708…8cd7
0x2b46c0…1669
4 touches
1 conflict
0x359866c7…de7b
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity