← previous blocknext block →recent activity
Analyzing
Block #106,381,499
16 transactions · 16 stateful · 2026-09-20 05:37:04 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,381,499 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w010w111w212w313w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7cee389f…adef
0x34b655…2a6f
10 touches
10 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe8058ec4…ebac
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xdde1e1b8…a9da
0x34ae4d…3fc5
4 touches
1 conflict
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0x2f74f175…9287
0x34ae4d…3fc5
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
10 conflicts on slot 0x7cee389f2c…0cadef
Audit this contract →
← previous block·next block →recent activity