← previous blocknext block →recent activity
Analyzing
Block #83,945,986
14 transactions · 13 stateful · 2026-06-27 02:54:16 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,945,986 · 14 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
1w02w14w05w110w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x82437f64…3f11
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x57c8db9d…3979
0x34b655…2a6f
5 touches
3 conflicts
0x00966e54…7d1d
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0x170e4e4c…2b90
0x34b655…2a6f
4 touches
1 conflict
0x1e212d2d…8ac8
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
3 conflicts on slot 0x82437f64ff…143f11
Audit this contract →
← previous block·next block →recent activity