← previous blocknext block →recent activity
Analyzing
Block #93,240,013
14 transactions · 13 stateful · 2026-08-05 03:30:27 UTC
Parallelism
64/100
Blocked
46%
Avg conflicts / tx
1.07
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,240,013 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w38w410w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x246bc8b8…8c1f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xcda18b0b…6a4c
0x34b655…2a6f
6 touches
3 conflicts
0x216ffe66…1f94
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…642d
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x246bc8b8df…838c1f
Audit this contract →
← previous block·next block →recent activity