← previous blocknext block →recent activity
Analyzing
Block #83,844,125
20 transactions · 14 stateful · 2026-06-26 15:35:08 UTC
Parallelism
90/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,844,125 · 20 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
2w03w04w18w09w114w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b33f5b9…4bab
0x34b655…2a6f
4 touches
1 conflict
0x8f29aace…1a6c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x73351a57…afa5
0x40c49f…2af0
2 touches
0 conflicts
0x9951b6b0…22d0
0x40c49f…2af0
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 0x5b33f5b941…b54bab
Audit this contract →
← previous block·next block →recent activity