← previous blocknext block →recent activity
Analyzing
Block #83,191,989
20 transactions · 16 stateful · 2026-06-23 15:01:33 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.3
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,191,989 · 20 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
1w02w19w010w115w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x262a4cd6…9d3c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcf827da3…f2a5
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdc54eb34…fe58
0x34b655…2a6f
4 touches
1 conflict
0xea4316bc…6b4f
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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
1 conflict on slot 0x262a4cd64b…489d3c
Audit this contract →
← previous block·next block →recent activity