← previous blocknext block →recent activity
Analyzing
Block #93,445,984
10 transactions · 10 stateful · 2026-08-05 20:46:02 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,445,984 · 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
1w02w13w04w15w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xf279bfea…5fd6
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x06ec4ccb…b190
0x34b655…2a6f
2 touches
0 conflicts
0x25d292ed…5531
0x34b655…2a6f
2 touches
0 conflicts
0x25e6f91a…a6a4
0x34b655…2a6f
2 touches
0 conflicts
0x2860b9bb…282c
0x34b655…2a6f
2 touches
0 conflicts
0x30ae635d…5e67
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity