← previous blocknext block →recent activity
Analyzing
Block #99,871,138
37 transactions · 33 stateful · 2026-08-28 10:11:05 UTC
Parallelism
84/100
Blocked
67%
Avg conflicts / tx
1.24
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,871,138 · 37 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w28w09w110w311w012w113w218w320w121w224w325w427w428w129w334w235w336w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf61f287…3f4e
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0xf5b5f7…6d70
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x443a3e47…f4a4
0x065c9d…c394
6 touches
3 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
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 0xcf61f28790…6b3f4e
Audit this contract →
← previous block·next block →recent activity