← previous blocknext block →recent activity
Analyzing
Block #80,240,392
19 transactions · 14 stateful · 2026-06-09 22:51:26 UTC
Parallelism
89/100
Blocked
29%
Avg conflicts / tx
0.26
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,240,392 · 19 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
2w03w14w15w112w015w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e5f2a94…4732
0x34b655…2a6f
4 touches
1 conflict
0x1da1c6cb…bb3f
0x34b655…2a6f
4 touches
1 conflict
0xebda062f…e87a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0xfe39a1f7…8eb0
0x34b655…2a6f
4 touches
1 conflict
0xac26b848…0e92
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
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: Perpl
1 conflict on slot 0x0e5f2a945b…554732
Audit this contract →
← previous block·next block →recent activity