← previous blocknext block →recent activity
Analyzing
Block #104,024,563
20 transactions · 18 stateful · 2026-09-11 23:19:23 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
1.45
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,024,563 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w29w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x949fc5d9…55f3
0x34b655…2a6f
16 touches
28 conflicts
0xa4f6516c…aad0
0x34b655…2a6f
16 touches
28 conflicts
0xc6d445ec…8564
0x34b655…2a6f
16 touches
28 conflicts
0xc7954a60…d294
0x34b655…2a6f
16 touches
28 conflicts
0x49890ced…6f23
0x34b655…2a6f
16 touches
28 conflicts
0xf1595b25…ef40
0x34b655…2a6f
16 touches
28 conflicts
0x10379e8d…3675
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
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
28 conflicts on slot 0x949fc5d98c…1955f3
Audit this contract →
← previous block·next block →recent activity