← previous blocknext block →recent activity
Analyzing
Block #102,043,074
14 transactions · 13 stateful · 2026-09-05 00:30:06 UTC
Parallelism
57/100
Blocked
46%
Avg conflicts / tx
1.07
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,043,074 · 14 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
1w02w15w06w110w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3cf50d44…961b
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x247cfb80…cca8
0x34b655…2a6f
6 touches
3 conflicts
0xd5982776…4846
0x34b655…2a6f
6 touches
3 conflicts
0x0c3d5d7f…d23c
0x34b655…2a6f
5 touches
3 conflicts
0x01315072…0e2d
0x34b655…2a6f
4 touches
1 conflict
0x83b29ee8…b345
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
6 conflicts on slot 0x3cf50d44a0…1e961b
Audit this contract →
← previous block·next block →recent activity