← previous blocknext block →recent activity
Analyzing
Block #82,538,102
25 transactions · 18 stateful · 2026-06-20 14:08:59 UTC
Parallelism
88/100
Blocked
39%
Avg conflicts / tx
0.32
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,538,102 · 25 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w08w010w011w112w213w014w117w118w119w122w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66312019…f62e
0xe7cd86…c82d
4 touches
1 conflict
0x00000000…0000
0xacf82e…3500
4 touches
1 conflict
0x54060017…c0c6
0xe7cd86…c82d
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x08913286…f0df
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x8b305a3b…1c35
0x34b655…2a6f
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: 0xe7cd86e1…0fc82d
1 conflict on slot 0x66312019ae…9cf62e
Audit this contract →
← previous block·next block →recent activity