← previous blocknext block →recent activity
Analyzing
Block #104,804,134
25 transactions · 22 stateful · 2026-09-14 17:14:51 UTC
Parallelism
76/100
Blocked
41%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,804,134 · 25 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
1w02w15w211w012w113w214w316w017w418w119w522w024w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2202504e…fad0
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x6d787177…e955
0x34b655…2a6f
8 touches
6 conflicts
0x9210e826…1414
0x34b655…2a6f
8 touches
6 conflicts
0xa3c8bb2f…5c75
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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
10 conflicts on slot 0x2202504ef1…9ffad0
Audit this contract →
← previous block·next block →recent activity