← previous blocknext block →recent activity
Analyzing
Block #92,171,971
13 transactions · 13 stateful · 2026-08-01 09:55:51 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.54
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,171,971 · 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
1w02w13w14w06w27w08w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34a1ee7e…fb20
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x003f6298…b756
0x7b9256…1fb2
4 touches
1 conflict
0xfb518d84…1ac9
0x7b9256…1fb2
4 touches
1 conflict
0xfb518d84…1aca
0x7b9256…1fb2
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x03c38bff…f48f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
3 conflicts on slot 0x34a1ee7e95…7cfb20
Audit this contract →
← previous block·next block →recent activity