← previous blocknext block →recent activity
Analyzing
Block #80,340,102
18 transactions · 11 stateful · 2026-06-10 09:56:10 UTC
Parallelism
89/100
Blocked
18%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,340,102 · 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
5w06w09w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1728ed63…499c
0xea1b8e…c5ec
4 touches
1 conflict
0xb6b74ae0…8d5e
0xea1b8e…c5ec
4 touches
1 conflict
0x408e66bb…3d6b
0x34b655…2a6f
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
2 touches
0 conflicts
0xea63e6e2…1ee1
0x1efe02…37d6
2 touches
0 conflicts
0xf1c3aac6…e559
0x1efe02…37d6
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
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: LeverUp: LeverUp
1 conflict on slot 0x1728ed6317…a9499c
Audit this contract →
← previous block·next block →recent activity