← previous blocknext block →recent activity
Analyzing
Block #93,063,622
10 transactions · 7 stateful · 2026-08-04 12:42:16 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,063,622 · 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f1b7b03…17fd
0x34b655…2a6f
4 touches
1 conflict
0x0110331c…b891
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0a42683d…6f4f
0x34b655…2a6f
2 touches
0 conflicts
0x0a42683d…6f50
0x34b655…2a6f
2 touches
0 conflicts
0x5d7e0e69…e6d1
0x34b655…2a6f
2 touches
0 conflicts
0x5d7e0e69…e6d2
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 0x4f1b7b0324…c517fd
Audit this contract →
← previous block·next block →recent activity