← previous blocknext block →recent activity
Analyzing
Block #93,338,513
14 transactions · 13 stateful · 2026-08-05 11:45:42 UTC
Parallelism
57/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,338,513 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w37w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0c9bb84…ba20
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xac3e4969…39e9
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x0e22f39d…b92b
0x34b655…2a6f
4 touches
1 conflict
0x0e987a39…7fe0
0x34b655…2a6f
4 touches
1 conflict
0x4d5053d1…3b7d
0x34b655…2a6f
4 touches
1 conflict
0x4ecb58c4…ac20
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 0xa0c9bb84f1…e2ba20
Audit this contract →
← previous block·next block →recent activity