← previous blocknext block →recent activity
Analyzing
Block #81,524,524
13 transactions · 11 stateful · 2026-06-15 21:29:58 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #81,524,524 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w29w010w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9b4eff6…c3ef
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x9d3f2124…725b
0x2a68ba…90c5
2 touches
1 conflict
0xb182933f…46ed
0x754704…b603
2 touches
1 conflict
0x78871d64…3385
0x065c9d…c394
2 touches
0 conflicts
0xc92fd15f…5e1a
0x065c9d…c394
2 touches
0 conflicts
0x09a15b10…2639
0x754704…b603
2 touches
0 conflicts
0x354a0cfa…bcc7
0x754704…b603
2 touches
0 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
1 conflict on slot 0xb9b4eff6b7…8cc3ef
Audit this contract →
← previous block·next block →recent activity