← previous blocknext block →recent activity
Analyzing
Block #83,412,876
19 transactions · 17 stateful · 2026-06-24 15:37:18 UTC
Parallelism
89/100
Blocked
29%
Avg conflicts / tx
0.32
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,412,876 · 19 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
2w04w05w17w08w110w011w112w014w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7b070f…db9a
0x34b655…2a6f
4 touches
1 conflict
0xe02484a6…c32e
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb87
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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: Perpl
1 conflict on slot 0xec7b070f86…6fdb9a
Audit this contract →
← previous block·next block →recent activity