← previous blocknext block →recent activity
Analyzing
Block #104,159,763
14 transactions · 13 stateful · 2026-09-12 10:47:19 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,159,763 · 14 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
2w04w15w26w39w010w111w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b4bb0a5…5845
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xfda69449…1d3b
0x34b655…2a6f
6 touches
3 conflicts
0xd7e4217d…7c6b
0x34b655…2a6f
6 touches
3 conflicts
0x5666db7d…5dc4
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x02698894…0e5a
0x34b655…2a6f
5 touches
3 conflicts
0x9ff94a68…7ae8
0x34b655…2a6f
5 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
3 conflicts on slot 0x6b4bb0a55e…e45845
Audit this contract →
← previous block·next block →recent activity