← previous blocknext block →recent activity
Analyzing
Block #84,092,590
13 transactions · 10 stateful · 2026-06-27 19:11:02 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,092,590 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8617c94f…6193
0x34b655…2a6f
4 touches
1 conflict
0xbd68c7c7…40b3
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x81c2c8c6…99e0
0x065c9d…c394
2 touches
0 conflicts
0x88d2d5a0…ffd4
0x065c9d…c394
2 touches
0 conflicts
0xfd91f14e…f3d5
0x065c9d…c394
2 touches
0 conflicts
0xff96dc9b…93d7
0x065c9d…c394
2 touches
0 conflicts
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
1 conflict on slot 0x8617c94f69…ee6193
Audit this contract →
← previous block·next block →recent activity