← previous blocknext block →recent activity
Analyzing
Block #105,683,240
13 transactions · 13 stateful · 2026-09-17 19:00:22 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,683,240 · 13 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
1w02w18w09w210w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24025143…5c6b
0x34b655…2a6f
8 touches
6 conflicts
0xf48fa71e…bb52
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x6e6a8155…9636
0x34b655…2a6f
4 touches
1 conflict
0x8849e72f…b522
0x34b655…2a6f
4 touches
1 conflict
0x8ed2a645…b3ce
0x34b655…2a6f
4 touches
1 conflict
0x8fd9063d…2f57
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
6 conflicts on slot 0x24025143bf…315c6b
Audit this contract →
← previous block·next block →recent activity