← previous blocknext block →recent activity
Analyzing
Block #102,058,265
19 transactions · 19 stateful · 2026-09-05 01:47:03 UTC
Parallelism
79/100
Blocked
53%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,058,265 · 19 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
1w02w13w14w25w39w110w011w112w013w115w116w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25fd5528…ff50
0x34b655…2a6f
7 touches
6 conflicts
0xeb4304a5…dd06
0x34b655…2a6f
6 touches
3 conflicts
0x3d13406e…eff1
0x34b655…2a6f
6 touches
3 conflicts
0x4dffc33e…068d
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xa2c04336…e4c0
0x34b655…2a6f
6 touches
3 conflicts
0xa8e524cc…c8e3
0x34b655…2a6f
6 touches
3 conflicts
0xaaf36ccb…f35c
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x25fd5528d1…82ff50
Audit this contract →
← previous block·next block →recent activity