← previous blocknext block →recent activity
Analyzing
Block #104,198,273
22 transactions · 22 stateful · 2026-09-12 14:02:41 UTC
Parallelism
68/100
Blocked
36%
Avg conflicts / tx
1.23
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,198,273 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w06w212w313w415w416w518w619w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8aeebcbe…1eb9
0x34b655…2a6f
12 touches
15 conflicts
0x1408e7c7…f324
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x803eb45d…00bd
0x34b655…2a6f
6 touches
3 conflicts
0x3270d9f8…099a
0x34b655…2a6f
6 touches
3 conflicts
0x6d955786…1327
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
15 conflicts on slot 0x8aeebcbe99…c71eb9
Audit this contract →
← previous block·next block →recent activity