← previous blocknext block →recent activity
Analyzing
Block #104,195,324
22 transactions · 22 stateful · 2026-09-12 13:47:41 UTC
Parallelism
50/100
Blocked
55%
Avg conflicts / tx
2.45
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #104,195,324 · 22 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w27w38w49w513w614w716w817w918w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x45de70d9…e1dc
0x34b655…2a6f
16 touches
28 conflicts
0x798a6c42…de14
0x34b655…2a6f
16 touches
28 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xe66201d4…84f1
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x60f63d67…5ba0
0x34b655…2a6f
8 touches
6 conflicts
0x93ed9a2c…64d4
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
28 conflicts on slot 0x45de70d9be…64e1dc
Audit this contract →
← previous block·next block →recent activity