← previous blocknext block →recent activity
Analyzing
Block #93,504,491
21 transactions · 20 stateful · 2026-08-06 01:40:10 UTC
Parallelism
81/100
Blocked
45%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,504,491 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w08w19w110w315w016w117w218w319w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
6 touches
3 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0xe1fc046b…9af3
0x34b655…2a6f
6 touches
3 conflicts
0x74fa4437…c4b2
0x851145…3f07
6 touches
3 conflicts
0x55ce57a3…f7d1
0x34b655…2a6f
5 touches
3 conflicts
0x7a12283f…b18a
0x2b46c0…1669
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity