← previous blocknext block →recent activity
Analyzing
Block #83,204,205
9 transactions · 8 stateful · 2026-06-23 16:23:20 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,204,205 · 9 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c48b3ac…a03c
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xb6b7c45d…9d5a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0573bc44…c14f
0x065c9d…c394
2 touches
0 conflicts
0x281d7715…c2ea
0x065c9d…c394
2 touches
0 conflicts
0x2e10fc47…b75a
0x065c9d…c394
2 touches
0 conflicts
0x6d08df92…07c3
0x065c9d…c394
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 0x1c48b3acf3…40a03c
Audit this contract →
← previous block·next block →recent activity