← previous blocknext block →recent activity
Analyzing
Block #94,482,014
15 transactions · 14 stateful · 2026-08-09 11:52:08 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1.2
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,482,014 · 15 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
2w03w14w15w28w39w410w011w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5502e1cc…3910
0x34b655…2a6f
8 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0xf4f9cac7…fd98
0x34b655…2a6f
8 touches
6 conflicts
0xc43b7aac…bd73
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x155e52ca…fac7
0x34b655…2a6f
4 touches
1 conflict
0x2bea6eae…9f7b
0x34b655…2a6f
4 touches
1 conflict
0x441923dd…d1a6
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
6 conflicts on slot 0x5502e1cc19…1a3910
Audit this contract →
← previous block·next block →recent activity