← previous blocknext block →recent activity
Analyzing
Block #83,673,057
20 transactions · 18 stateful · 2026-06-25 20:33:37 UTC
Parallelism
80/100
Blocked
28%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,673,057 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w09w210w211w117w018w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9863393c…ce7b
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0x571cb36d…3b3d
0x34b655…2a6f
6 touches
3 conflicts
0x374fc18a…6998
0x34b655…2a6f
4 touches
1 conflict
0x3a41a4c0…aaf1
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
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
3 conflicts on slot 0x9863393ce4…4cce7b
Audit this contract →
← previous block·next block →recent activity