← previous blocknext block →recent activity
Analyzing
Block #83,617,952
21 transactions · 14 stateful · 2026-06-25 14:25:49 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,617,952 · 21 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
2w05w110w011w117w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb67571a4…012d
0x34b655…2a6f
4 touches
1 conflict
0xb6ed511f…6b68
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xda7f9bd2…e332
0x34b655…2a6f
4 touches
1 conflict
0xecd87a39…d9c5
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x3f7ad3a0…de3b
0x34b655…2a6f
4 touches
1 conflict
0x445b51c5…0be4
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: Perpl
1 conflict on slot 0xb67571a4f2…4b012d
Audit this contract →
← previous block·next block →recent activity