← previous blocknext block →recent activity
Analyzing
Block #105,843,433
17 transactions · 17 stateful · 2026-09-18 08:27:58 UTC
Parallelism
71/100
Blocked
65%
Avg conflicts / tx
1.24
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,843,433 · 17 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
1w02w13w14w25w36w17w09w010w111w213w114w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x2f0f281c…9e72
0x34b655…2a6f
6 touches
3 conflicts
0x3c9b10c1…d791
0x34b655…2a6f
6 touches
3 conflicts
0x48828733…fd48
0x34b655…2a6f
6 touches
3 conflicts
0x69d2053b…935a
0x34b655…2a6f
6 touches
3 conflicts
0x97394169…cfc0
0x34b655…2a6f
6 touches
3 conflicts
0x9daafdf9…bb53
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
6 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity