← previous blocknext block →recent activity
Analyzing
Block #104,201,410
14 transactions · 14 stateful · 2026-09-12 14:18:38 UTC
Parallelism
71/100
Blocked
21%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,201,410 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
9w011w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8868587f…e5be
0x34b655…2a6f
8 touches
6 conflicts
0x3270d9f8…099a
0x34b655…2a6f
4 touches
1 conflict
0x3522af60…d679
0x34b655…2a6f
4 touches
1 conflict
0x0dd3bdfb…7537
0x34b655…2a6f
4 touches
1 conflict
0x70a7b5d6…fe0e
0x34b655…2a6f
4 touches
1 conflict
0x94dfe52d…824a
0x34b655…2a6f
4 touches
1 conflict
0x0dd3bdfb…7538
0x34b655…2a6f
4 touches
1 conflict
0xd7908b5f…56b9
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 0x8868587f35…eae5be
Audit this contract →
← previous block·next block →recent activity