← previous blocknext block →recent activity
Analyzing
Block #105,402,778
20 transactions · 17 stateful · 2026-09-16 19:28:45 UTC
Parallelism
90/100
Blocked
12%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,402,778 · 20 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbef2ead…dee0
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0xe2a2183a…af0b
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x3d1a888b…ba9d
0x34b655…2a6f
2 touches
0 conflicts
0x4a438561…8235
0x34b655…2a6f
2 touches
0 conflicts
0x5b7f4325…8970
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 0xbbef2ead54…73dee0
Audit this contract →
← previous block·next block →recent activity