← previous blocknext block →recent activity
Analyzing
Block #104,870,862
20 transactions · 17 stateful · 2026-09-14 22:51:37 UTC
Parallelism
70/100
Blocked
35%
Avg conflicts / tx
0.55
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,870,862 · 20 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
4w06w17w213w314w415w517w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7443f37…eb79
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x3e3f27ce…580c
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xf2880574…4e73
0x34b655…2a6f
6 touches
3 conflicts
0x25614b41…2c66
0x34b655…2a6f
6 touches
3 conflicts
0x5b37bb6b…aaff
0x34b655…2a6f
4 touches
1 conflict
0xac32f75b…5647
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 0xd7443f3786…61eb79
Audit this contract →
← previous block·next block →recent activity