← previous blocknext block →recent activity
Analyzing
Block #83,642,072
29 transactions · 21 stateful · 2026-06-25 17:07:00 UTC
Parallelism
90/100
Blocked
19%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,642,072 · 29 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w09w112w014w015w116w122w027w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd68c7c7…40b3
0x34b655…2a6f
6 touches
3 conflicts
0xf06c2cf5…61bd
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x55384053…4a1f
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xfd40a14e…a76e
0x065c9d…c394
3 touches
1 conflict
0x27953357…8168
0xd32edf…ff58
3 touches
1 conflict
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
3 conflicts on slot 0xbd68c7c758…bd40b3
Audit this contract →
← previous block·next block →recent activity