← previous blocknext block →recent activity
Analyzing
Block #104,877,303
25 transactions · 23 stateful · 2026-09-14 23:24:02 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
1.2
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,877,303 · 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
2w03w16w27w08w111w316w417w419w520w222w323w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdcd58096…bb7a
0x34b655…2a6f
12 touches
15 conflicts
0x9b4f173c…94e6
0x34b655…2a6f
10 touches
10 conflicts
0xac389ba9…8b45
0x34b655…2a6f
10 touches
10 conflicts
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0xef3f5637…f47c
0x34b655…2a6f
8 touches
6 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7dd96c96…7335
0x34b655…2a6f
6 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
15 conflicts on slot 0xdcd5809626…a9bb7a
Audit this contract →
← previous block·next block →recent activity