← previous blocknext block →recent activity
Analyzing
Block #92,547,477
9 transactions · 9 stateful · 2026-08-02 17:24:20 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,547,477 · 9 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
1w02w13w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4663cfe3…262d
0x34b655…2a6f
4 touches
1 conflict
0x745a7fd6…5fea
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xe61e515e…9e7f
0x34b655…2a6f
4 touches
1 conflict
0x0ff353ce…a594
0x34b655…2a6f
2 touches
0 conflicts
0x17b5c6a1…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x17f5dec8…3332
0x34b655…2a6f
2 touches
0 conflicts
0x248e43aa…7287
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 0x4663cfe301…91262d
Audit this contract →
← previous block·next block →recent activity