← previous blocknext block →recent activity
Analyzing
Block #100,144,015
27 transactions · 21 stateful · 2026-08-29 09:05:33 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,144,015 · 27 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
5w07w18w010w113w214w015w318w019w420w221w126w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61571888…b392
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x3dd02e95…7536
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0x5655f5c3…6b75
0x34b655…2a6f
4 touches
1 conflict
0x574499ff…0aec
0x34b655…2a6f
4 touches
1 conflict
0x69ee34d1…30f8
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 0x6157188898…efb392
Audit this contract →
← previous block·next block →recent activity