← previous blocknext block →recent activity
Analyzing
Block #83,453,541
20 transactions · 18 stateful · 2026-06-24 20:08:57 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,453,541 · 20 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
1w03w05w16w18w09w112w013w116w217w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f0e8a2f…a850
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
4 touches
1 conflict
0x2886e2bc…6ab8
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0x7f225f35…4353
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: Perpl
3 conflicts on slot 0x8f0e8a2f96…7ba850
Audit this contract →
← previous block·next block →recent activity