← previous blocknext block →recent activity
Analyzing
Block #81,407,284
14 transactions · 13 stateful · 2026-06-15 08:28:40 UTC
Parallelism
64/100
Blocked
31%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #81,407,284 · 14 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
4w05w16w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x587911c7…9e01
0x34b655…2a6f
8 touches
6 conflicts
0xf3fbc9b8…ab58
0x34b655…2a6f
6 touches
3 conflicts
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0xf5adc2ae…ac32
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
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
6 conflicts on slot 0x587911c74f…109e01
Audit this contract →
← previous block·next block →recent activity