← previous blocknext block →recent activity
Analyzing
Block #80,256,397
22 transactions · 14 stateful · 2026-06-10 00:38:08 UTC
Parallelism
82/100
Blocked
36%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,256,397 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w28w09w119w020w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0xb1f0701d…4f4a
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x16452d34…7c10
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
0x34b655…2a6f
4 touches
1 conflict
0x90f07a4f…d932
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: Perpl
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity