← previous blocknext block →recent activity
Analyzing
Block #83,494,210
19 transactions · 18 stateful · 2026-06-25 00:40:18 UTC
Parallelism
63/100
Blocked
56%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,494,210 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w07w08w19w210w311w412w513w614w116w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0659a3f…90d9
0x000000…a032
14 touches
21 conflicts
0xee70c256…3665
0x754704…b603
14 touches
21 conflicts
0x34b1e500…7687
0x754704…b603
14 touches
21 conflicts
0xd0fdd34f…60c2
0x754704…b603
14 touches
21 conflicts
0x00000000…000f
0x78999c…f371
14 touches
21 conflicts
0x00000000…000b
0x78999c…f371
14 touches
21 conflicts
0x00000000…000b
0x754704…b603
14 touches
21 conflicts
0xffc2f21e…b393
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: 0x00000000…7da032
21 conflicts on slot 0xe0659a3f75…9f90d9
Audit this contract →
← previous block·next block →recent activity