← previous blocknext block →recent activity
Analyzing
Block #105,870,188
19 transactions · 17 stateful · 2026-09-18 10:42:40 UTC
Parallelism
74/100
Blocked
29%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,870,188 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w110w212w313w414w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09784fd2…7130
0x34b655…2a6f
8 touches
6 conflicts
0x9dccd2a9…2790
0x34b655…2a6f
8 touches
6 conflicts
0x7b67f6cf…0aab
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x16a8cd0c…27bd
0x34b655…2a6f
4 touches
1 conflict
0x56d57b49…25a5
0x34b655…2a6f
4 touches
1 conflict
0x7d6b9af1…9a38
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0x09784fd21d…087130
Audit this contract →
← previous block·next block →recent activity