← previous blocknext block →recent activity
Analyzing
Block #93,230,821
15 transactions · 13 stateful · 2026-08-05 02:44:14 UTC
Parallelism
87/100
Blocked
8%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,230,821 · 15 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
5w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x651d4cdd…66a6
0x34b655…2a6f
4 touches
1 conflict
0x81238469…de5d
0x34b655…2a6f
4 touches
1 conflict
0x651d4cdd…66a7
0x34b655…2a6f
4 touches
1 conflict
0x4e6b752c…6813
0x34b655…2a6f
4 touches
1 conflict
0x11db128b…1153
0x34b655…2a6f
2 touches
0 conflicts
0x1321736a…43e3
0x34b655…2a6f
2 touches
0 conflicts
0x34d95d94…3a16
0x34b655…2a6f
2 touches
0 conflicts
0x44abd9f6…6b3f
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 0x651d4cddab…b766a6
Audit this contract →
← previous block·next block →recent activity