← previous blocknext block →recent activity
Analyzing
Block #104,870,621
15 transactions · 14 stateful · 2026-09-14 22:50:24 UTC
Parallelism
47/100
Blocked
64%
Avg conflicts / tx
2.2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,870,621 · 15 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w16w27w38w411w512w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7443f37…eb79
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xfda3b445…e5c1
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x54c8c0a4…812a
0x34b655…2a6f
4 touches
1 conflict
0x80bc3112…747d
0x34b655…2a6f
4 touches
1 conflict
0x86bbab41…5590
0x34b655…2a6f
4 touches
1 conflict
0x9210e826…1414
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 0xd7443f3786…61eb79
Audit this contract →
← previous block·next block →recent activity