← previous blocknext block →recent activity
Analyzing
Block #84,494,461
27 transactions · 23 stateful · 2026-06-29 15:48:44 UTC
Parallelism
85/100
Blocked
48%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,494,461 · 27 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
1w02w03w16w28w09w110w211w012w113w214w318w119w320w021w125w026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
8 touches
6 conflicts
0x56785e37…a197
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xe75cebb6…6b36
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xce4481d8…3c2f
0x065c9d…c394
4 touches
1 conflict
0xa9db7b4d…2957
0x40c49f…2af0
4 touches
1 conflict
0x08943ea2…ed03
0x754704…b603
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: 0xd637b38f…c64160
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity