← previous blocknext block →recent activity
Analyzing
Block #93,247,779
10 transactions · 10 stateful · 2026-08-05 04:09:29 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,247,779 · 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
2w04w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x931bd7a5…b6b9
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x4f9b503e…4422
0x34b655…2a6f
4 touches
1 conflict
0x286711a5…b3bf
0x34b655…2a6f
4 touches
1 conflict
0x1df4c9d2…76e1
0x34b655…2a6f
2 touches
0 conflicts
0x4bd46536…17e5
0x34b655…2a6f
2 touches
0 conflicts
0x565326bb…ae7e
0x34b655…2a6f
2 touches
0 conflicts
0x588ba065…f516
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 0x931bd7a585…f2b6b9
Audit this contract →
← previous block·next block →recent activity