← previous blocknext block →recent activity
Analyzing
Block #83,453,404
14 transactions · 12 stateful · 2026-06-24 20:08:02 UTC
Parallelism
86/100
Blocked
25%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,453,404 · 14 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
1w04w07w08w110w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfadc118d…5d64
0x34b655…2a6f
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x126a0344…4465
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x76477ddf…b8f8
0xc8689a…ee79
4 touches
1 conflict
0x393dfd73…ff57
0x34b655…2a6f
4 touches
1 conflict
0x5e75a40f…5eed
0x34b655…2a6f
4 touches
1 conflict
0xe9425fe7…1711
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
1 conflict on slot 0xfadc118dc2…025d64
Audit this contract →
← previous block·next block →recent activity