← previous blocknext block →recent activity
Analyzing
Block #93,302,638
14 transactions · 11 stateful · 2026-08-05 08:45:20 UTC
Parallelism
71/100
Blocked
27%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,302,638 · 14 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
2w05w06w17w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51d03c9d…57a7
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x725a56fa…ce3c
0x34b655…2a6f
4 touches
1 conflict
0x7ac265cd…0253
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 0x51d03c9de0…c357a7
Audit this contract →
← previous block·next block →recent activity