← previous blocknext block →recent activity
Analyzing
Block #83,204,100
8 transactions · 7 stateful · 2026-06-23 16:22:37 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,204,100 · 8 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6fd65c0…3a8a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x46d5a052…ff2e
0x34b655…2a6f
3 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x00076632…7bf7
0x34b655…2a6f
2 touches
0 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x16dce2e7…6f05
0x34b655…2a6f
2 touches
0 conflicts
0x7e17e82a…9748
0x34b655…2a6f
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 0xe6fd65c0f9…793a8a
Audit this contract →
← previous block·next block →recent activity