← previous blocknext block →recent activity
Analyzing
Block #102,276,031
19 transactions · 19 stateful · 2026-09-05 20:10:57 UTC
Parallelism
84/100
Blocked
37%
Avg conflicts / tx
0.53
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,276,031 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w16w07w28w113w015w117w218w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38aa1898…fdf5
0xb53c4f…8a01
6 touches
3 conflicts
0x8b9e2d47…9675
0x188d58…ea8e
6 touches
3 conflicts
0x1342557a…df31
0x27bc99…9a93
6 touches
3 conflicts
0xb3dee783…2711
0x27bc99…9a93
6 touches
3 conflicts
0x1dc71894…1884
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x17359e55…7914
0x188d58…ea8e
6 touches
3 conflicts
0x0a85a226…83ba
0x1b6862…e19c
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: 0xb53c4fb3…2b8a01
3 conflicts on slot 0x38aa189812…48fdf5
Audit this contract →
← previous block·next block →recent activity