← previous blocknext block →recent activity
Analyzing
Block #81,481,848
24 transactions · 21 stateful · 2026-06-15 16:45:37 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #81,481,848 · 24 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
1w02w13w24w05w06w27w18w39w310w413w014w117w223w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x48acfd83…7ef0
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xacdf56b3…e33c
0xa6afd3…d132
6 touches
3 conflicts
0xee3b1b53…77dd
0xa6afd3…d132
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x11998eac…f99f
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: 0x40c49f17…d22af0
3 conflicts on slot 0x48acfd8394…2b7ef0
Audit this contract →
← previous block·next block →recent activity