← previous blocknext block →recent activity
Analyzing
Block #83,844,767
13 transactions · 9 stateful · 2026-06-26 15:39:26 UTC
Parallelism
85/100
Blocked
22%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,844,767 · 13 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
1w03w14w010w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x0fde64da…aa3e
0x2a68ba…90c5
4 touches
1 conflict
0x5c591136…d322
0x34b655…2a6f
4 touches
1 conflict
0xb65644e3…33ce
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x43fc5037…b7d4
0x851145…3f07
3 touches
1 conflict
0x6aed4b37…0ee7
0x754704…b603
2 touches
0 conflicts
0xa1087a5c…66c4
0x754704…b603
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 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity