← previous blocknext block →recent activity
Analyzing
Block #103,987,196
15 transactions · 14 stateful · 2026-09-11 20:09:20 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #103,987,196 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w013w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xa6e7f29c…5d8c
0x34b655…2a6f
4 touches
1 conflict
0x29a58269…011a
0x34b655…2a6f
2 touches
0 conflicts
0x2f9ef618…0c39
0x34b655…2a6f
2 touches
0 conflicts
0x42d9b0a9…f4a1
0x34b655…2a6f
2 touches
0 conflicts
0x5c7b5ec0…0764
0x34b655…2a6f
2 touches
0 conflicts
0x70c220e5…d202
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity