← previous blocknext block →recent activity
Analyzing
Block #92,530,984
22 transactions · 22 stateful · 2026-08-02 16:01:24 UTC
Parallelism
68/100
Blocked
55%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,530,984 · 22 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
2w03w14w25w36w47w58w69w010w011w112w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000b
0x90c374…be45
14 touches
21 conflicts
0x00000000…000a
0x90c374…be45
14 touches
21 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x17bbe4f8…08c5
0xe52b14…7230
4 touches
1 conflict
0x3cebc8f1…975c
0xe52b14…7230
4 touches
1 conflict
0x58733c38…f2cd
0xe52b14…7230
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: 0x90c3747c…0ebe45
21 conflicts on slot 0x0000000000…00000b
Audit this contract →
← previous block·next block →recent activity