← previous blocknext block →recent activity
Analyzing
Block #93,487,007
14 transactions · 14 stateful · 2026-08-06 00:12:16 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,487,007 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e18c945…dfcd
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x4e135144…4167
0x34b655…2a6f
4 touches
1 conflict
0xeff551a4…61cf
0x1efe02…37d6
2 touches
0 conflicts
0x04e17b28…d9ef
0x34b655…2a6f
2 touches
0 conflicts
0x04e17b28…d9f0
0x34b655…2a6f
2 touches
0 conflicts
0x055b5b38…8737
0x34b655…2a6f
2 touches
0 conflicts
0x1a889cb6…dee3
0xea1b8e…c5ec
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
1 conflict on slot 0x6e18c94551…89dfcd
Audit this contract →
← previous block·next block →recent activity