← previous blocknext block →recent activity
Analyzing
Block #92,974,611
10 transactions · 8 stateful · 2026-08-04 05:14:18 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,974,611 · 10 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff28ee17…414e
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x04d6a0b0…59c5
0x34b655…2a6f
2 touches
0 conflicts
0x06ad0dfb…39a2
0x34b655…2a6f
2 touches
0 conflicts
0x27d80c30…98d9
0x34b655…2a6f
2 touches
0 conflicts
0x6de6b8cb…64fb
0x34b655…2a6f
2 touches
0 conflicts
0x764f042f…f8b8
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 0xff28ee1740…f0414e
Audit this contract →
← previous block·next block →recent activity