← previous blocknext block →recent activity
Analyzing
Block #100,921,014
16 transactions · 13 stateful · 2026-09-01 02:18:53 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,921,014 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w08w19w112w013w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2827ae77…4368
0x34b655…2a6f
4 touches
1 conflict
0x2b18b0a3…c5a2
0x34b655…2a6f
4 touches
1 conflict
0x5359bce1…be67
0x34b655…2a6f
4 touches
1 conflict
0x6caf33e2…c261
0x34b655…2a6f
4 touches
1 conflict
0x72e5021c…c006
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity