← previous blocknext block →recent activity
Analyzing
Block #93,370,315
11 transactions · 9 stateful · 2026-08-05 14:25:35 UTC
Parallelism
73/100
Blocked
44%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,370,315 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w17w29w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc08384da…ecb7
0x34b655…2a6f
4 touches
1 conflict
0x772ab420…c2f6
0x34b655…2a6f
4 touches
1 conflict
0x92339d95…0800
0x0000a8…8888
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xbfa7b68f…e546
0x34b655…2a6f
4 touches
1 conflict
0x23df630a…22a5
0x34b655…2a6f
2 touches
0 conflicts
0x2fd12b6c…02cc
0x34b655…2a6f
2 touches
0 conflicts
0x6a26eb13…b01c
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 0xc08384da3a…ebecb7
Audit this contract →
← previous block·next block →recent activity