← previous blocknext block →recent activity
Analyzing
Block #71,344,117
8 transactions · 5 stateful · 2026-04-29 17:44:11 UTC
Parallelism
75/100
Blocked
20%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,344,117 · 8 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
3w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8abcc19…3d83
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1e8342c2…7d52
0x065c9d…c394
2 touches
0 conflicts
0x6135e37a…e361
0x065c9d…c394
2 touches
0 conflicts
0x6cfa5539…6aec
0x065c9d…c394
2 touches
0 conflicts
0x7107d627…2a0b
0x065c9d…c394
2 touches
0 conflicts
0xdba41736…9115
0x065c9d…c394
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 0xa8abcc1955…203d83
Audit this contract →
← previous block·next block →recent activity