← previous blocknext block →recent activity
Analyzing
Block #83,453,193
30 transactions · 21 stateful · 2026-06-24 20:06:37 UTC
Parallelism
83/100
Blocked
48%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,453,193 · 30 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
2w03w18w09w110w211w313w018w119w220w321w022w424w028w129w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x8f0e8a2f…a850
0x34b655…2a6f
6 touches
3 conflicts
0x1e7117d6…8817
0x34b655…2a6f
4 touches
1 conflict
0x97c67486…27fe
0x34b655…2a6f
4 touches
1 conflict
0xde53ca4f…19e9
0x34b655…2a6f
4 touches
1 conflict
0xec06bf19…fcc3
0x34b655…2a6f
4 touches
1 conflict
0xf7cd1236…1e31
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity