← previous blocknext block →recent activity
Analyzing
Block #92,068,780
13 transactions · 11 stateful · 2026-08-01 01:16:51 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,068,780 · 13 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
1w02w13w06w17w08w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff3dbbcd…5060
0x34b655…2a6f
4 touches
1 conflict
0x17739dc8…3671
0x34b655…2a6f
4 touches
1 conflict
0x1b23c223…997c
0x34b655…2a6f
4 touches
1 conflict
0xecd87a39…d9c5
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4ae3b148…7ed2
0x34b655…2a6f
4 touches
1 conflict
0x58959811…75a0
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 0xff3dbbcd67…0c5060
Audit this contract →
← previous block·next block →recent activity