← previous blocknext block →recent activity
Analyzing
Block #83,210,627
17 transactions · 15 stateful · 2026-06-23 17:06:17 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,210,627 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w010w111w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x6d122bab…e279
0xd32edf…ff58
3 touches
1 conflict
0x6c5beec2…bcac
0x0a4fcb…a602
2 touches
0 conflicts
0x6c5beec2…bcad
0x0a4fcb…a602
2 touches
0 conflicts
0x9a052754…e945
0x0a4fcb…a602
2 touches
0 conflicts
0x9f96eede…9b20
0x0a4fcb…a602
2 touches
0 conflicts
0x6bd9b2de…7d72
0x0f2610…0edc
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
1 conflict on slot 0x8b305a3b6b…0c1c35
Audit this contract →
← previous block·next block →recent activity