← previous blocknext block →recent activity
Analyzing
Block #105,402,473
38 transactions · 34 stateful · 2026-09-16 19:27:12 UTC
Parallelism
84/100
Blocked
65%
Avg conflicts / tx
1.37
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,402,473 · 38 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w27w38w010w119w220w322w423w124w126w228w129w531w232w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed252c0a…b47e
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x80398c66…f3cc
0x34b655…2a6f
8 touches
6 conflicts
0x3018a378…d7bb
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xf5b5f7…6d70
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
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
10 conflicts on slot 0xed252c0ae5…3eb47e
Audit this contract →
← previous block·next block →recent activity