← previous blocknext block →recent activity
Analyzing
Block #94,798,714
28 transactions · 24 stateful · 2026-08-10 14:26:31 UTC
Parallelism
71/100
Blocked
54%
Avg conflicts / tx
1.11
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,798,714 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w27w38w09w010w113w014w215w316w417w418w520w221w626w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03aa8b26…118a
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xa4f80979…4d71
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xa605468c…1bfc
0x2b46c0…1669
4 touches
1 conflict
0x2840c278…bbc7
0x34b655…2a6f
4 touches
1 conflict
0x29ec5458…704a
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
10 conflicts on slot 0x03aa8b260f…60118a
Audit this contract →
← previous block·next block →recent activity