← previous blocknext block →recent activity
Analyzing
Block #104,868,735
17 transactions · 16 stateful · 2026-09-14 22:40:55 UTC
Parallelism
71/100
Blocked
56%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,868,735 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w06w17w28w39w410w111w112w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1470cae0…177e
0x34b655…2a6f
10 touches
10 conflicts
0xfa09be5a…1e79
0x34b655…2a6f
10 touches
10 conflicts
0x7b67f6cf…0aab
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x98b14f9b…08b3
0x34b655…2a6f
8 touches
6 conflicts
0xbf303bde…ce5a
0x34b655…2a6f
6 touches
3 conflicts
0xdd9da06d…95a6
0x40c49f…2af0
4 touches
1 conflict
0x31f1efce…7865
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
10 conflicts on slot 0x1470cae0a7…6b177e
Audit this contract →
← previous block·next block →recent activity