← previous blocknext block →recent activity
Analyzing
Block #105,366,167
27 transactions · 26 stateful · 2026-09-16 16:24:24 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.59
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,366,167 · 27 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w18w09w010w113w314w117w120w021w422w523w625w826w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
12 touches
15 conflicts
0x7dd96c96…7335
0x34b655…2a6f
6 touches
3 conflicts
0x99c8b719…5f38
0x34b655…2a6f
6 touches
3 conflicts
0x79ec4509…1f61
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x93f55e4e…62a3
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
21 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity