← previous blocknext block →recent activity
Analyzing
Block #83,690,937
26 transactions · 24 stateful · 2026-06-25 22:32:56 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.35
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,690,937 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w09w111w012w113w014w121w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x571cb36d…3b3d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xbc9aaf19…8cfd
0x34b655…2a6f
6 touches
3 conflicts
0x4467ecee…e95b
0x34b655…2a6f
6 touches
3 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
6 touches
3 conflicts
0x4cc838ad…4525
0x34b655…2a6f
4 touches
1 conflict
0x549cc733…17ac
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 0x571cb36db3…a33b3d
Audit this contract →
← previous block·next block →recent activity