← previous blocknext block →recent activity
Analyzing
Block #83,628,590
23 transactions · 19 stateful · 2026-06-25 15:36:57 UTC
Parallelism
91/100
Blocked
16%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,628,590 · 23 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
1w02w17w08w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31658946…5d47
0x34b655…2a6f
4 touches
1 conflict
0x6767aeb1…eabc
0x34b655…2a6f
4 touches
1 conflict
0x785889c9…0603
0x34b655…2a6f
4 touches
1 conflict
0x8ae827f1…aa36
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0xf06c2cf5…61bd
0x34b655…2a6f
4 touches
1 conflict
0x76477ddf…b8f8
0xc8689a…ee79
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 0x3165894656…cc5d47
Audit this contract →
← previous block·next block →recent activity