← previous blocknext block →recent activity
Analyzing
Block #80,166,026
21 transactions · 18 stateful · 2026-06-09 14:35:27 UTC
Parallelism
86/100
Blocked
28%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,166,026 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w26w18w09w014w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xcdc1731c…b91a
0x34b655…2a6f
4 touches
1 conflict
0xa8abcc19…3d83
0xea1b8e…c5ec
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0xeb6cddba…30d0
0x065c9d…c394
4 touches
1 conflict
0x23c64216…4e86
0x065c9d…c394
3 touches
1 conflict
0x13616e0c…0732
0xd32edf…ff58
3 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: 0xfd44b351…7f00d1
1 conflict on slot 0x00bac0131a…bba28c
Audit this contract →
← previous block·next block →recent activity