← previous blocknext block →recent activity
Analyzing
Block #105,682,973
16 transactions · 14 stateful · 2026-09-17 18:59:01 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,682,973 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w07w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34e61077…195a
0x34b655…2a6f
4 touches
1 conflict
0x08c5d8d8…c7c1
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x29bbfffb…ea4a
0x34b655…2a6f
2 touches
0 conflicts
0x2b59ae54…89f8
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x34e6107763…13195a
Audit this contract →
← previous block·next block →recent activity