← previous blocknext block →recent activity
Analyzing
Block #93,563,409
17 transactions · 17 stateful · 2026-08-06 06:36:20 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
1.24
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,563,409 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w07w18w19w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a2c83a3…a29a
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0x1bf8d2af…d140
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x2c01bd80…2967
0x34b655…2a6f
8 touches
6 conflicts
0xa8c5904c…e1a7
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x7a2c83a30a…f3a29a
Audit this contract →
← previous block·next block →recent activity