← previous blocknext block →recent activity
Analyzing
Block #81,617,034
15 transactions · 14 stateful · 2026-06-16 07:46:00 UTC
Parallelism
87/100
Blocked
7%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,617,034 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w012w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x98fc5672…13c7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x43081395…4e15
0x065c9d…c394
2 touches
0 conflicts
0x8e348981…da58
0x065c9d…c394
2 touches
0 conflicts
0x9d9d1aee…06a1
0x065c9d…c394
2 touches
0 conflicts
0xa6072bd5…3f34
0x065c9d…c394
2 touches
0 conflicts
0xc4f6183f…b162
0x065c9d…c394
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity