← previous blocknext block →recent activity
Analyzing
Block #100,985,384
26 transactions · 23 stateful · 2026-09-01 07:42:41 UTC
Parallelism
85/100
Blocked
43%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,985,384 · 26 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
1w02w14w05w17w18w111w212w013w114w216w218w321w025w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe0c4f53…4d97
0x34b655…2a6f
8 touches
6 conflicts
0x3ee8b564…4c49
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x15698ac9…2a46
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xd5b10148…e637
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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 0xbe0c4f53b2…0e4d97
Audit this contract →
← previous block·next block →recent activity