← previous blocknext block →recent activity
Analyzing
Block #102,323,188
16 transactions · 16 stateful · 2026-09-06 00:09:50 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,323,188 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8fbd1a7e…17e4
0x34b655…2a6f
4 touches
1 conflict
0xa9988419…9f45
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0eff0903…8165
0x754704…b603
2 touches
0 conflicts
0x777c9106…162a
0x754704…b603
2 touches
0 conflicts
0x68c08dd2…be14
0x99c7a7…8bf0
2 touches
0 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
1 conflict on slot 0x8fbd1a7ee7…6617e4
Audit this contract →
← previous block·next block →recent activity