← previous blocknext block →recent activity
Analyzing
Block #81,407,863
24 transactions · 21 stateful · 2026-06-15 08:32:31 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
1.25
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #81,407,863 · 24 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
6w07w110w116w017w118w219w320w421w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x59dccbd8…2bf6
0x34b655…2a6f
8 touches
6 conflicts
0xe03af632…a920
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x961da181…ed17
0x34b655…2a6f
6 touches
3 conflicts
0xded5ec0c…f0fc
0x34b655…2a6f
6 touches
3 conflicts
0xbc04d98e…a484
0x34b655…2a6f
5 touches
3 conflicts
0x21d22421…0b7a
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity