← previous blocknext block →recent activity
Analyzing
Block #105,433,973
33 transactions · 25 stateful · 2026-09-16 22:05:46 UTC
Parallelism
85/100
Blocked
40%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,433,973 · 33 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
5w07w08w19w111w012w113w014w119w020w125w226w328w429w332w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x26c599c1…706c
0x34b655…2a6f
4 touches
1 conflict
0x48717abe…be13
0x34b655…2a6f
4 touches
1 conflict
0x4b024b98…8f37
0x34b655…2a6f
4 touches
1 conflict
0x58799a46…7030
0x34b655…2a6f
4 touches
1 conflict
0x5aed1bd2…7afa
0x34b655…2a6f
4 touches
1 conflict
0x788e2096…c37f
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity