← previous blocknext block →recent activity
Analyzing
Block #104,810,964
17 transactions · 17 stateful · 2026-09-14 17:49:14 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,810,964 · 17 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
1w03w14w05w06w17w210w311w412w515w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x059e0ac0…0267
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x1be6e729…bd32
0x34b655…2a6f
4 touches
1 conflict
0xca42df4c…eb9a
0x34b655…2a6f
4 touches
1 conflict
0x3949ae21…c6b8
0x34b655…2a6f
4 touches
1 conflict
0xffcb6dec…487a
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 0x059e0ac09d…0f0267
Audit this contract →
← previous block·next block →recent activity