← previous blocknext block →recent activity
Analyzing
Block #84,072,781
18 transactions · 16 stateful · 2026-06-27 16:58:53 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,072,781 · 18 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
4w05w010w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8177fbe3…306e
0x34b655…2a6f
4 touches
1 conflict
0x0b16149e…7d4d
0x065c9d…c394
4 touches
1 conflict
0xd31b69bc…8e62
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xcd9a9bc6…b25f
0x065c9d…c394
2 touches
0 conflicts
0xd98011fc…7b57
0x065c9d…c394
2 touches
0 conflicts
0xac2a0273…7212
0x34b655…2a6f
2 touches
0 conflicts
0x2dbc727c…778b
0x754704…b603
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 0x8177fbe39f…ae306e
Audit this contract →
← previous block·next block →recent activity