← previous blocknext block →recent activity
Analyzing
Block #94,487,269
13 transactions · 13 stateful · 2026-08-09 12:18:34 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,487,269 · 13 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
1w02w13w04w16w07w18w29w310w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba1ef4c2…ef4e
0x34b655…2a6f
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x45ff93a4…6fee
0x065c9d…c394
5 touches
3 conflicts
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x36188fc2…5f06
0x34b655…2a6f
4 touches
1 conflict
0x4228eb58…8905
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 0xba1ef4c22d…eeef4e
Audit this contract →
← previous block·next block →recent activity