← previous blocknext block →recent activity
Analyzing
Block #106,389,378
20 transactions · 19 stateful · 2026-09-20 06:16:43 UTC
Parallelism
80/100
Blocked
53%
Avg conflicts / tx
0.9
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,389,378 · 20 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
1w02w03w14w25w010w211w112w213w314w215w316w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46b02b98…e1e7
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x1c840894…764a
0x34b655…2a6f
6 touches
3 conflicts
0xaa35a811…8c66
0x34b655…2a6f
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
3 conflicts on slot 0x46b02b985d…a1e1e7
Audit this contract →
← previous block·next block →recent activity