← previous blocknext block →recent activity
Analyzing
Block #93,064,513
9 transactions · 8 stateful · 2026-08-04 12:46:45 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,064,513 · 9 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
2w03w14w28w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xebac0f82…a49c
0x34b655…2a6f
6 touches
3 conflicts
0x9fbc6a76…9c29
0x34b655…2a6f
4 touches
1 conflict
0xb8ea0ed7…b68c
0x34b655…2a6f
4 touches
1 conflict
0xc7c09b47…3e3c
0x34b655…2a6f
4 touches
1 conflict
0x41527b68…5ad4
0x34b655…2a6f
4 touches
1 conflict
0x76c4467d…ce28
0x34b655…2a6f
4 touches
1 conflict
0x70e3da66…674a
0x34b655…2a6f
2 touches
0 conflicts
0x73c29f06…fffc
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
3 conflicts on slot 0xebac0f82ec…86a49c
Audit this contract →
← previous block·next block →recent activity