← previous blocknext block →recent activity
Analyzing
Block #104,869,103
27 transactions · 26 stateful · 2026-09-14 22:42:46 UTC
Parallelism
74/100
Blocked
38%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,869,103 · 27 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w08w110w213w114w215w316w417w518w621w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9722304…6ed0
0x34b655…2a6f
14 touches
21 conflicts
0x3b6e959d…158f
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xab612fbf…82c8
0x34b655…2a6f
10 touches
10 conflicts
0xf5d99264…de4e
0x34b655…2a6f
10 touches
10 conflicts
0xe31707f7…691e
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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
21 conflicts on slot 0xd97223041d…366ed0
Audit this contract →
← previous block·next block →recent activity