← previous blocknext block →recent activity
Analyzing
Block #102,528,364
22 transactions · 18 stateful · 2026-09-06 17:29:39 UTC
Parallelism
86/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,528,364 · 22 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
2w03w16w09w111w017w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f9c6bd9…c66c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd6c976a1…1d47
0x34b655…2a6f
4 touches
1 conflict
0xd6c976a1…1d48
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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
1 conflict on slot 0x6f9c6bd9c9…dcc66c
Audit this contract →
← previous block·next block →recent activity