← previous blocknext block →recent activity
Analyzing
Block #82,273,628
17 transactions · 16 stateful · 2026-06-19 08:44:49 UTC
Parallelism
82/100
Blocked
25%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,273,628 · 17 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
2w03w15w06w115w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f58168d…ea24
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfe3d37ee…6e67
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x08913286…f0df
0x34b655…2a6f
4 touches
1 conflict
0x636fd21a…9978
0x34b655…2a6f
4 touches
1 conflict
0x1c243b1c…ea0f
0x40c49f…2af0
2 touches
0 conflicts
0x342fbbca…d443
0x40c49f…2af0
2 touches
0 conflicts
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
1 conflict on slot 0x6f58168d48…e3ea24
Audit this contract →
← previous block·next block →recent activity