← previous blocknext block →recent activity
Analyzing
Block #105,619,793
32 transactions · 25 stateful · 2026-09-17 13:40:58 UTC
Parallelism
75/100
Blocked
64%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,619,793 · 32 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w16w27w09w110w212w315w217w318w419w520w622w730w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0002
0xf5b5f7…6d70
10 touches
10 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
6 touches
3 conflicts
0x2242a1ee…5035
0x34b655…2a6f
4 touches
1 conflict
0x276c8e53…68f1
0x34b655…2a6f
4 touches
1 conflict
0x38c094c2…a251
0x34b655…2a6f
4 touches
1 conflict
0x51ce0ad3…dd3f
0x34b655…2a6f
4 touches
1 conflict
0x5b0a33d1…f825
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
28 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity