← previous blocknext block →recent activity
Analyzing
Block #76,087,985
22 transactions · 14 stateful · 2026-05-21 17:16:19 UTC
Parallelism
91/100
Blocked
29%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,087,985 · 22 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
1w02w13w010w012w117w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17b9a4d…7716
0xe1c8b7…3022
4 touches
1 conflict
0x67d846dd…358c
0x62c84c…7777
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x69cd5c19…88ca
0x9f3832…4ae4
4 touches
1 conflict
0x7cf5136f…ba69
0x9f3832…4ae4
4 touches
1 conflict
0xaa47606d…91ca
0x9f3832…4ae4
4 touches
1 conflict
0xaa47606d…91cb
0x9f3832…4ae4
4 touches
1 conflict
0xa164d951…1534
0xe1c8b7…3022
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: 0xe1c8b733…e33022
1 conflict on slot 0xd17b9a4dc2…ae7716
Audit this contract →
← previous block·next block →recent activity