← previous blocknext block →recent activity
Analyzing
Block #94,808,167
18 transactions · 17 stateful · 2026-08-10 15:14:04 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,808,167 · 18 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
2w03w14w06w18w09w010w112w214w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x201d7cf1…f7f2
0x34b655…2a6f
6 touches
3 conflicts
0xadaf61be…38bd
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x3464bbc5…a323
0xa6afd3…d132
4 touches
1 conflict
0x1cdfe548…d3aa
0x34b655…2a6f
4 touches
1 conflict
0x30ae635d…5e67
0x34b655…2a6f
4 touches
1 conflict
0x4e8c6085…e8a1
0x34b655…2a6f
4 touches
1 conflict
0x524f0872…0d12
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 0x201d7cf137…32f7f2
Audit this contract →
← previous block·next block →recent activity