← previous blocknext block →recent activity
Analyzing
Block #104,205,016
19 transactions · 19 stateful · 2026-09-12 14:36:59 UTC
Parallelism
68/100
Blocked
32%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,205,016 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w010w111w214w315w416w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac9e0b10…4f67
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x6dedaff6…161b
0x34b655…2a6f
10 touches
10 conflicts
0xb839a1e8…22b3
0x34b655…2a6f
4 touches
1 conflict
0xb339fa7e…132f
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x07d94be1…7fa8
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
15 conflicts on slot 0xac9e0b10d0…ec4f67
Audit this contract →
← previous block·next block →recent activity