← previous blocknext block →recent activity
Analyzing
Block #93,289,207
15 transactions · 14 stateful · 2026-08-05 07:37:48 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,289,207 · 15 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
5w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07a9a4ce…6b6e
0x34b655…2a6f
4 touches
1 conflict
0x242fd968…26ed
0x34b655…2a6f
4 touches
1 conflict
0x242fd968…26ee
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6a2521fa…2320
0x34b655…2a6f
4 touches
1 conflict
0xa69ba9e8…e56a
0x34b655…2a6f
4 touches
1 conflict
0xb15c58ec…bd83
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
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
1 conflict on slot 0x07a9a4ce12…1d6b6e
Audit this contract →
← previous block·next block →recent activity