← previous blocknext block →recent activity
Analyzing
Block #83,195,928
13 transactions · 11 stateful · 2026-06-23 15:27:55 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,195,928 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w09w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c73d3c9…94fd
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x77674e3c…0f43
0x34b655…2a6f
4 touches
1 conflict
0x11bf603c…1140
0x34b655…2a6f
4 touches
1 conflict
0x006c3b86…59a9
0x34b655…2a6f
4 touches
1 conflict
0xe1d1f14d…3ffb
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0xcfe06a18…b5b5
0x69df8a…6292
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 0x8c73d3c9b9…2b94fd
Audit this contract →
← previous block·next block →recent activity