← previous blocknext block →recent activity
Analyzing
Block #82,390,803
17 transactions · 13 stateful · 2026-06-19 21:46:59 UTC
Parallelism
76/100
Blocked
46%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,390,803 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w26w37w010w114w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x342fbbca…d443
0x40c49f…2af0
6 touches
3 conflicts
0xfee25e81…fe0e
0x40c49f…2af0
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0x1c27080f…8475
0x40c49f…2af0
4 touches
1 conflict
0xea1b8c07…b969
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity