← previous blocknext block →recent activity
Analyzing
Block #102,038,966
16 transactions · 16 stateful · 2026-09-05 00:09:19 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,038,966 · 16 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
1w05w010w111w213w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94e7f277…471b
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xbda78ea1…8309
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x247cfb80…cca8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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
3 conflicts on slot 0x94e7f27794…c6471b
Audit this contract →
← previous block·next block →recent activity