← previous blocknext block →recent activity
Analyzing
Block #106,393,334
17 transactions · 17 stateful · 2026-09-20 06:36:38 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.18
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,393,334 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w010w111w112w213w214w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x990cc6f8…0e7b
0x34b655…2a6f
10 touches
10 conflicts
0xe32e848a…851e
0x34b655…2a6f
10 touches
10 conflicts
0x8d175439…fb79
0x34b655…2a6f
8 touches
6 conflicts
0x2130a548…c1de
0x34b655…2a6f
8 touches
6 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
6 touches
3 conflicts
0x48ed1159…abe9
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 0x990cc6f828…0f0e7b
Audit this contract →
← previous block·next block →recent activity