← previous blocknext block →recent activity
Analyzing
Block #106,283,037
43 transactions · 30 stateful · 2026-09-19 21:21:34 UTC
Parallelism
88/100
Blocked
47%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,283,037 · 43 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
1w04w16w08w09w010w011w114w215w317w018w122w023w128w231w234w235w336w438w140w141w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36db5650…40b8
0x34b655…2a6f
10 touches
10 conflicts
0x86cea35b…bdff
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x4ee0b65a…6d40
0x34b655…2a6f
6 touches
3 conflicts
0x3b6e959d…158f
0x34b655…2a6f
6 touches
3 conflicts
0x70986451…c6bd
0x34b655…2a6f
6 touches
3 conflicts
0xb6111f03…4eda
0xd32edf…ff58
5 touches
3 conflicts
0x5b6af007…0f35
0x34b655…2a6f
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 0x36db56503d…fc40b8
Audit this contract →
← previous block·next block →recent activity