← previous blocknext block →recent activity
Analyzing
Block #93,345,297
10 transactions · 9 stateful · 2026-08-05 12:19:48 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,345,297 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66649bfc…6f75
0x34b655…2a6f
6 touches
3 conflicts
0x231ccc13…a7c6
0x34b655…2a6f
6 touches
3 conflicts
0x4abaedb1…65b9
0x34b655…2a6f
4 touches
1 conflict
0xe66201d4…84f1
0x34b655…2a6f
4 touches
1 conflict
0x41f1e2e5…2edf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xdcc30f96…83d7
0x34b655…2a6f
4 touches
1 conflict
0x66f7c9fa…39a3
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
3 conflicts on slot 0x66649bfc33…1d6f75
Audit this contract →
← previous block·next block →recent activity