← previous blocknext block →recent activity
Analyzing
Block #100,565,823
17 transactions · 16 stateful · 2026-08-30 20:31:45 UTC
Parallelism
59/100
Blocked
38%
Avg conflicts / tx
1.12
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,565,823 · 17 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
2w03w16w212w013w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xcf61f287…3f4e
0x34b655…2a6f
10 touches
10 conflicts
0x886db264…846e
0x34b655…2a6f
8 touches
6 conflicts
0xd6e60e7b…8ac0
0x34b655…2a6f
6 touches
3 conflicts
0xc8fb3c38…8c4e
0x34b655…2a6f
5 touches
3 conflicts
0x775a8ad3…8307
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 0x92385428ad…dc6941
Audit this contract →
← previous block·next block →recent activity