← previous blocknext block →recent activity
Analyzing
Block #105,410,711
24 transactions · 24 stateful · 2026-09-16 20:08:42 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,410,711 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w110w017w220w321w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc16f6da7…5399
0x34b655…2a6f
6 touches
3 conflicts
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0xb3870dbe…bef3
0x2a68ba…90c5
4 touches
1 conflict
0x2914814a…e9d9
0x34b655…2a6f
4 touches
1 conflict
0x2aa44a8f…16f5
0x34b655…2a6f
4 touches
1 conflict
0x5b6af007…0f35
0x34b655…2a6f
4 touches
1 conflict
0x6e7fac88…3607
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity