← previous blocknext block →recent activity
Analyzing
Block #100,610,916
23 transactions · 19 stateful · 2026-08-31 00:18:36 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
0.96
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,610,916 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w19w210w311w112w218w420w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3037bed…6b7c
0x34b655…2a6f
8 touches
6 conflicts
0xb7ce83b1…2c96
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x7e3d46e1…80a7
0x34b655…2a6f
4 touches
1 conflict
0xa496748e…8183
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
6 conflicts on slot 0xb3037bed3e…856b7c
Audit this contract →
← previous block·next block →recent activity