← previous blocknext block →recent activity
Analyzing
Block #83,453,197
31 transactions · 24 stateful · 2026-06-24 20:06:39 UTC
Parallelism
74/100
Blocked
54%
Avg conflicts / tx
1.16
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,453,197 · 31 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w29w010w111w113w217w018w119w220w321w422w523w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0xe6950848…9ff6
0x34b655…2a6f
10 touches
10 conflicts
0xe02484a6…c32e
0xc8689a…ee79
10 touches
10 conflicts
0xbeb10b8a…4ce5
0x34b655…2a6f
10 touches
10 conflicts
0xbfca3cd0…5023
0x34b655…2a6f
10 touches
10 conflicts
0x33b914cf…6964
0x34b655…2a6f
8 touches
6 conflicts
0x40970e69…da50
0x69df8a…6292
6 touches
3 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
6 touches
3 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
28 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity