← previous blocknext block →recent activity
Analyzing
Block #100,734,655
18 transactions · 17 stateful · 2026-08-31 10:41:03 UTC
Parallelism
72/100
Blocked
41%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,734,655 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w07w08w19w210w315w417w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb7b36bf…38db
0x34b655…2a6f
8 touches
6 conflicts
0x5d1ac445…5233
0x34b655…2a6f
8 touches
6 conflicts
0x94af8c30…94fb
0x34b655…2a6f
8 touches
6 conflicts
0xcd232ca9…031a
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x0463db49…5d05
0x34b655…2a6f
6 touches
3 conflicts
0xfdb6a6c8…31c4
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xfb7b36bff3…f438db
Audit this contract →
← previous block·next block →recent activity