← previous blocknext block →recent activity
Analyzing
Block #104,977,351
14 transactions · 13 stateful · 2026-09-15 07:47:28 UTC
Parallelism
86/100
Blocked
8%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #104,977,351 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fd9f955…e86b
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0xcd5c0ecb…4b5f
0x34b655…2a6f
4 touches
1 conflict
0x01315072…0e2d
0x34b655…2a6f
2 touches
0 conflicts
0x122a19fc…472a
0x34b655…2a6f
2 touches
0 conflicts
0x16fd070e…e9c4
0x34b655…2a6f
2 touches
0 conflicts
0x26c599c1…706c
0x34b655…2a6f
2 touches
0 conflicts
0x278c3873…20a0
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 0x0fd9f9554d…8fe86b
Audit this contract →
← previous block·next block →recent activity