← previous blocknext block →recent activity
Analyzing
Block #102,205,684
24 transactions · 23 stateful · 2026-09-05 14:14:33 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,205,684 · 24 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
1w02w13w04w05w16w07w28w09w314w416w018w119w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd868fb65…3b4a
0xe1c8b7…3022
10 touches
10 conflicts
0x00000000…00c9
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…641f
0x34b655…2a6f
10 touches
10 conflicts
0xc8c615d4…5da3
0x34b655…2a6f
10 touches
10 conflicts
0x44ed742f…63f5
0x3bd359…433a
10 touches
10 conflicts
0x4eb758b8…b13b
0x3bd359…433a
10 touches
10 conflicts
0xdf409966…6b16
0x3bd359…433a
10 touches
10 conflicts
0x00000000…0004
0x7aed55…0617
10 touches
10 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: 0xe1c8b733…e33022
10 conflicts on slot 0xd868fb65f1…2f3b4a
Audit this contract →
← previous block·next block →recent activity