← previous blocknext block →recent activity
Analyzing
Block #106,216,418
30 transactions · 30 stateful · 2026-09-19 15:46:16 UTC
Parallelism
77/100
Blocked
63%
Avg conflicts / tx
1.6
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,216,418 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w37w410w112w213w315w416w417w518w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe9dc3c58…d7ed
0x34b655…2a6f
12 touches
15 conflicts
0x94ed2e6a…c6b6
0x34b655…2a6f
12 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
12 touches
15 conflicts
0xe655004a…b829
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x394c3833…b4ae
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
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
15 conflicts on slot 0xe9dc3c58c2…3ed7ed
Audit this contract →
← previous block·next block →recent activity