← previous blocknext block →recent activity
Analyzing
Block #81,626,868
34 transactions · 20 stateful · 2026-06-16 08:51:28 UTC
Parallelism
79/100
Blocked
45%
Avg conflicts / tx
0.5
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #81,626,868 · 34 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w110w011w118w019w120w223w229w331w432w533w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x879d4311…78c4
0x34b655…2a6f
8 touches
6 conflicts
0x90f07a4f…d932
0x34b655…2a6f
6 touches
3 conflicts
0x1017e868…fcc2
0x34b655…2a6f
6 touches
3 conflicts
0x662257eb…a78c
0x34b655…2a6f
6 touches
3 conflicts
0x1045386d…cb89
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity