← previous blocknext block →recent activity
Analyzing
Block #93,471,937
14 transactions · 11 stateful · 2026-08-05 22:56:30 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,471,937 · 14 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
4w05w16w210w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x075dcfb7…1c3b
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc6b9bb4b…145a
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x2bd8c8ca…8dc6
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x50dbe610…177f
0x34b655…2a6f
4 touches
1 conflict
0xe3280296…788e
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 0x075dcfb7dc…741c3b
Audit this contract →
← previous block·next block →recent activity