← previous blocknext block →recent activity
Analyzing
Block #100,560,833
13 transactions · 12 stateful · 2026-08-30 20:06:40 UTC
Parallelism
77/100
Blocked
17%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,560,833 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaf89f45…ced6
0x34b655…2a6f
6 touches
3 conflicts
0x69619e6d…aa7e
0x34b655…2a6f
6 touches
3 conflicts
0x33000c0a…82c3
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x9a8482cc…8bee
0x34b655…2a6f
4 touches
1 conflict
0xccdc1094…8a94
0x34b655…2a6f
4 touches
1 conflict
0x45436af6…437f
0x99c7a7…8bf0
2 touches
0 conflicts
0x66300207…c47a
0x99c7a7…8bf0
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
3 conflicts on slot 0xfaf89f4544…89ced6
Audit this contract →
← previous block·next block →recent activity