← previous blocknext block →recent activity
Analyzing
Block #71,283,834
18 transactions · 15 stateful · 2026-04-29 11:02:24 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #71,283,834 · 18 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
1w02w14w05w114w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0efc210e…70ab
0x34b655…2a6f
4 touches
1 conflict
0xf6d214b0…8abe
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xb857c1…9be1
4 touches
1 conflict
0xa5583259…b4e0
0xd32edf…ff58
3 touches
1 conflict
0x7f39f18a…00b3
0x065c9d…c394
2 touches
0 conflicts
0x99c170b4…b0a4
0x065c9d…c394
2 touches
0 conflicts
0xcdc919aa…44b3
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: Perpl
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity