← previous blocknext block →recent activity
Analyzing
Block #84,364,001
38 transactions · 23 stateful · 2026-06-29 01:19:01 UTC
Parallelism
89/100
Blocked
39%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,364,001 · 38 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
1w03w05w17w08w09w116w017w122w223w124w227w233w234w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0xe75cebb6…6b36
0x065c9d…c394
6 touches
3 conflicts
0x11014089…6411
0x34b655…2a6f
4 touches
1 conflict
0x4f62463a…d390
0x34b655…2a6f
4 touches
1 conflict
0x75291f8b…3ac0
0x34b655…2a6f
4 touches
1 conflict
0x93641233…06f5
0x34b655…2a6f
4 touches
1 conflict
0x98af2a4f…5ec1
0x34b655…2a6f
4 touches
1 conflict
0xc098579d…5607
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: 0x681e908b…e1ae09
3 conflicts on slot 0x0d622e34f9…000000
Audit this contract →
← previous block·next block →recent activity