← previous blocknext block →recent activity
Analyzing
Block #100,983,294
21 transactions · 20 stateful · 2026-09-01 07:32:10 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,983,294 · 21 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
1w02w14w15w29w010w111w212w317w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a100e05…c541
0x34b655…2a6f
8 touches
6 conflicts
0xd6113c0f…0a4b
0x34b655…2a6f
8 touches
6 conflicts
0xc0c143b1…108b
0x34b655…2a6f
8 touches
6 conflicts
0xd2fd6de4…1729
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x6b1259e6…4e13
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x15698ac9…2a46
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 0x9a100e057a…2ac541
Audit this contract →
← previous block·next block →recent activity