← previous blocknext block →recent activity
Analyzing
Block #82,193,501
24 transactions · 21 stateful · 2026-06-18 23:50:32 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,193,501 · 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
1w02w15w26w27w38w39w410w412w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffa7d0a4…b10a
0x40c49f…2af0
10 touches
10 conflicts
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0x342fbbca…d443
0x40c49f…2af0
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x5581d709…ab77
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c5
0x1b6862…e19c
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
10 conflicts on slot 0xffa7d0a419…63b10a
Audit this contract →
← previous block·next block →recent activity