← previous blocknext block →recent activity
Analyzing
Block #93,455,729
28 transactions · 25 stateful · 2026-08-05 21:35:01 UTC
Parallelism
86/100
Blocked
12%
Avg conflicts / tx
0.21
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,455,729 · 28 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
2w07w18w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fd87a64…6651
0x34b655…2a6f
8 touches
6 conflicts
0x1507536e…933f
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x9ba6ae4a…90cb
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x282f129e…8f33
0x34b655…2a6f
4 touches
1 conflict
0x52cef1b0…0e4e
0x34b655…2a6f
4 touches
1 conflict
0x8ed3c6fe…7be1
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
6 conflicts on slot 0x0fd87a64db…786651
Audit this contract →
← previous block·next block →recent activity