← previous blocknext block →recent activity
Analyzing
Block #100,618,819
12 transactions · 8 stateful · 2026-08-31 00:58:21 UTC
Parallelism
83/100
Blocked
13%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,618,819 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
10w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0462262d…a368
0x34b655…2a6f
4 touches
1 conflict
0x556a9a7a…b0ae
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x886db264…846e
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1c645adf…cd53
0x34b655…2a6f
3 touches
1 conflict
0x4e135144…4167
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x0462262d7c…7ea368
Audit this contract →
← previous block·next block →recent activity