← previous blocknext block →recent activity
Analyzing
Block #104,165,193
17 transactions · 16 stateful · 2026-09-12 11:14:50 UTC
Parallelism
47/100
Blocked
56%
Avg conflicts / tx
2.59
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #104,165,193 · 17 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w26w310w411w513w614w715w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2844358e…898f
0x34b655…2a6f
18 touches
36 conflicts
0x705a9a1a…db08
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
12 touches
15 conflicts
0x64275949…d698
0x34b655…2a6f
10 touches
10 conflicts
0x6b89ce6f…cc35
0x34b655…2a6f
8 touches
6 conflicts
0x6507044e…bcd6
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0x2844358e6d…fe898f
Audit this contract →
← previous block·next block →recent activity