← previous blocknext block →recent activity
Analyzing
Block #106,185,590
18 transactions · 16 stateful · 2026-09-19 13:11:04 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,185,590 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfda729a6…3a4e
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x56409df0…27cd
0x34b655…2a6f
4 touches
1 conflict
0x7cc0979d…5617
0x34b655…2a6f
4 touches
1 conflict
0x9167c873…748f
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
1 conflict on slot 0xfda729a6e6…be3a4e
Audit this contract →
← previous block·next block →recent activity