← previous blocknext block →recent activity
Analyzing
Block #104,195,591
71 transactions · 70 stateful · 2026-09-12 13:49:02 UTC
Parallelism
93/100
Blocked
9%
Avg conflicts / tx
0.18
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,195,591 · 71 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w110w211w112w267w368w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc52c928e…995a
0x34b655…2a6f
6 touches
3 conflicts
0x3111a64f…eb7f
0x34b655…2a6f
6 touches
3 conflicts
0x64275949…d698
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0x0fe1e6e0…f553
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
10 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity