← previous blocknext block →recent activity
Analyzing
Block #102,568,271
56 transactions · 53 stateful · 2026-09-06 20:52:01 UTC
Parallelism
93/100
Blocked
8%
Avg conflicts / tx
0.13
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,568,271 · 56 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w111w112w254w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x50e35017…7073
0x34b655…2a6f
8 touches
6 conflicts
0x53c41998…7d52
0x34b655…2a6f
6 touches
3 conflicts
0xfb682e7d…dde9
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x155e52ca…fac7
0x34b655…2a6f
4 touches
1 conflict
0x2e179963…86f3
0x34b655…2a6f
4 touches
1 conflict
0x4188cc5f…2d2e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0x50e35017b1…bf7073
Audit this contract →
← previous block·next block →recent activity