← previous blocknext block →recent activity
Analyzing
Block #93,373,025
15 transactions · 13 stateful · 2026-08-05 14:39:13 UTC
Parallelism
73/100
Blocked
54%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,373,025 · 15 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
1w02w13w04w15w26w28w311w113w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfecb18c0…01ed
0x34b655…2a6f
8 touches
6 conflicts
0xc651d5a8…d62d
0x40c49f…2af0
4 touches
1 conflict
0x3c21f1b2…d98d
0x34b655…2a6f
4 touches
1 conflict
0x47c24931…9b04
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xa03c2a35…52e6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfed09e59…a493
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 0xfecb18c068…6e01ed
Audit this contract →
← previous block·next block →recent activity