← previous blocknext block →recent activity
Analyzing
Block #100,605,545
20 transactions · 20 stateful · 2026-08-30 23:51:35 UTC
Parallelism
60/100
Blocked
65%
Avg conflicts / tx
1.6
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,605,545 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w07w28w19w110w213w114w215w316w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 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
0xc95f91db…a901
0x34b655…2a6f
8 touches
6 conflicts
0xe7aef4d2…32cb
0x34b655…2a6f
6 touches
3 conflicts
0x7a8cad7f…48cd
0x34b655…2a6f
5 touches
3 conflicts
0x18a01188…42f0
0x851145…3f07
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity