← previous blocknext block →recent activity
Analyzing
Block #93,406,370
11 transactions · 11 stateful · 2026-08-05 17:26:53 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,406,370 · 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
2w03w16w17w28w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c60fbcf…8744
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
0x34b655…2a6f
4 touches
1 conflict
0x898d9b8a…d1ef
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc6000ba5…8d65
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
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 0x6c60fbcffc…878744
Audit this contract →
← previous block·next block →recent activity