← previous blocknext block →recent activity
Analyzing
Block #100,919,942
22 transactions · 18 stateful · 2026-09-01 02:13:30 UTC
Parallelism
82/100
Blocked
44%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,919,942 · 22 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
1w02w16w09w110w212w013w114w215w217w318w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2827ae77…4368
0x34b655…2a6f
6 touches
3 conflicts
0x0778475b…bd75
0x2a68ba…90c5
6 touches
3 conflicts
0x49e90d60…d8bc
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x76305519…5d58
0x065c9d…c394
5 touches
3 conflicts
0x87d39100…7270
0x851145…3f07
4 touches
1 conflict
0x4edf87e6…e14b
0x065c9d…c394
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
3 conflicts on slot 0x2827ae778d…a84368
Audit this contract →
← previous block·next block →recent activity