← previous blocknext block →recent activity
Analyzing
Block #92,546,127
18 transactions · 13 stateful · 2026-08-02 17:17:33 UTC
Parallelism
89/100
Blocked
23%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,546,127 · 18 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
4w09w112w014w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x524f0872…0d12
0x34b655…2a6f
4 touches
1 conflict
0x745a7fd6…5fea
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x262d5015…771b
0x34b655…2a6f
3 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
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 0x524f087203…e70d12
Audit this contract →
← previous block·next block →recent activity