← previous blocknext block →recent activity
Analyzing
Block #82,272,863
17 transactions · 13 stateful · 2026-06-19 08:39:44 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,272,863 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w07w110w011w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c5c7e52…01b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x00000000…0002
0xaa7ee7…f0e4
4 touches
1 conflict
0xcb4ddc4a…d956
0x065c9d…c394
3 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0028
0x1b6862…e19c
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 0x8c5c7e5233…9a01b8
Audit this contract →
← previous block·next block →recent activity