← previous blocknext block →recent activity
Analyzing
Block #105,606,008
33 transactions · 30 stateful · 2026-09-17 12:31:34 UTC
Parallelism
79/100
Blocked
57%
Avg conflicts / tx
1.18
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,606,008 · 33 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
1w02w13w04w05w16w27w38w19w211w312w418w119w423w224w325w426w527w630w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x386d08f4…5a01
0x34b655…2a6f
10 touches
12 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x425c881c…b17f
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
8 touches
6 conflicts
0x1747fe24…ac3f
0x34b655…2a6f
6 touches
3 conflicts
0x81ceb686…4df3
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
12 conflicts on slot 0x386d08f44a…fc5a01
Audit this contract →
← previous block·next block →recent activity