← previous blocknext block →recent activity
Analyzing
Block #93,577,704
15 transactions · 14 stateful · 2026-08-06 07:48:11 UTC
Parallelism
87/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,577,704 · 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
3w04w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9af63a6a…6821
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37a
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37b
0x34b655…2a6f
4 touches
1 conflict
0x818b12b4…8b19
0x34b655…2a6f
3 touches
1 conflict
0x8af47133…0a8a
0x34b655…2a6f
3 touches
1 conflict
0x0e4000ee…afb9
0x34b655…2a6f
2 touches
0 conflicts
0x14002e42…475a
0x34b655…2a6f
2 touches
0 conflicts
0x1e302fd3…642c
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 0x9af63a6a5b…5c6821
Audit this contract →
← previous block·next block →recent activity