← previous blocknext block →recent activity
Analyzing
Block #105,618,485
31 transactions · 24 stateful · 2026-09-17 13:34:23 UTC
Parallelism
77/100
Blocked
54%
Avg conflicts / tx
1.03
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,618,485 · 31 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
2w05w07w08w19w010w111w113w214w015w116w119w321w022w323w424w525w629w430w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa17ae02d…5031
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd1448207…452d
0x34b655…2a6f
6 touches
3 conflicts
0x232df012…c608
0x34b655…2a6f
6 touches
3 conflicts
0x5b6af007…0f35
0x34b655…2a6f
6 touches
3 conflicts
0x68531239…e9a3
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 0xa17ae02da8…5e5031
Audit this contract →
← previous block·next block →recent activity