← previous blocknext block →recent activity
Analyzing
Block #92,057,459
15 transactions · 13 stateful · 2026-08-01 00:19:54 UTC
Parallelism
53/100
Blocked
54%
Avg conflicts / tx
1.4
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,057,459 · 15 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w37w49w510w613w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x465440fd…c9df
0x34b655…2a6f
12 touches
15 conflicts
0x7b55198a…b946
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x38c6ff01…689f
0x34b655…2a6f
6 touches
3 conflicts
0x4e58f1d6…2fca
0x34b655…2a6f
6 touches
3 conflicts
0xd25be779…0648
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
15 conflicts on slot 0x465440fd8c…a7c9df
Audit this contract →
← previous block·next block →recent activity