← previous blocknext block →recent activity
Analyzing
Block #105,855,103
20 transactions · 18 stateful · 2026-09-18 09:26:45 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,855,103 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w17w28w312w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x18cf84a6…09e4
0x34b655…2a6f
4 touches
1 conflict
0x1e63ce19…13c8
0x34b655…2a6f
4 touches
1 conflict
0x21d22421…0b7a
0x34b655…2a6f
4 touches
1 conflict
0x4681609f…6493
0x34b655…2a6f
4 touches
1 conflict
0x4d1e384e…979c
0x34b655…2a6f
4 touches
1 conflict
0x4f3d1bb8…76b3
0x34b655…2a6f
4 touches
1 conflict
0x554bc428…1432
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity