← previous blocknext block →recent activity
Analyzing
Block #76,284,260
12 transactions · 11 stateful · 2026-05-22 15:03:21 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,284,260 · 12 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
1w02w14w05w16w08w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf590a66a…0bf7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0xed07b7…b3b5
4 touches
1 conflict
0xbd25225a…c493
0xc39161…2de7
4 touches
1 conflict
0x2ea01b4c…c231
0xc39161…2de7
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x3e49348b…9445
0x34b655…2a6f
4 touches
1 conflict
0xc56d6548…50a4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
1 conflict on slot 0xf590a66ad2…db0bf7
Audit this contract →
← previous block·next block →recent activity