← previous blocknext block →recent activity
Analyzing
Block #100,588,391
51 transactions · 36 stateful · 2026-08-30 22:25:17 UTC
Parallelism
74/100
Blocked
69%
Avg conflicts / tx
1.75
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #100,588,391 · 51 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w08w19w010w012w120w123w125w226w027w328w129w230w232w233w334w335w436w542w444w645w746w848w1049w1150w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x886db264…846e
0x34b655…2a6f
10 touches
10 conflicts
0x1d9154e7…8821
0x34b655…2a6f
8 touches
6 conflicts
0x55192654…91fe
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x522e20b4…fbc4
0x34b655…2a6f
7 touches
6 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
55 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity