← previous blocknext block →recent activity
Analyzing
Block #83,662,004
15 transactions · 14 stateful · 2026-06-25 19:19:55 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,662,004 · 15 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
2w03w14w29w011w113w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc983cab3…daa5
0x34b655…2a6f
8 touches
6 conflicts
0xc1526f9e…82d5
0x34b655…2a6f
6 touches
3 conflicts
0x28d49795…afeb
0x34b655…2a6f
4 touches
1 conflict
0x374fc18a…6998
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5a5dd7b4…fba4
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
0x34b655…2a6f
4 touches
1 conflict
0x627e4c8a…e889
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
6 conflicts on slot 0xc983cab3f0…33daa5
Audit this contract →
← previous block·next block →recent activity