← previous blocknext block →recent activity
Analyzing
Block #84,428,702
20 transactions · 18 stateful · 2026-06-29 08:30:10 UTC
Parallelism
90/100
Blocked
17%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,428,702 · 20 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
6w07w18w010w015w016w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c8d6dd6…d61a
0xea1b8e…c5ec
4 touches
1 conflict
0x9c8d6dd6…d61d
0xea1b8e…c5ec
4 touches
1 conflict
0xd8eb2d31…2ac0
0xea1b8e…c5ec
4 touches
1 conflict
0xfecd05e7…296f
0xea1b8e…c5ec
4 touches
1 conflict
0xfecd05e7…2970
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x9560013d…8caf
0xfd44b3…00d1
4 touches
1 conflict
0xea02471d…1542
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: LeverUp: LeverUp
1 conflict on slot 0x9c8d6dd61f…1ad61a
Audit this contract →
← previous block·next block →recent activity